Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 64aec6df1a532c38b633cf2ab3aaa9d5ca79463f1d94410f7bd56a62bebe1931

Tx prefix hash: 6d843161903260abeb51ba8d2261d7ca5a22c7c4e243ced70dc73f7a6238de4c
Tx public key: 8334f4a53477f8c086227e9be821ca1c1ad578c46f37a2171f271562b046506a
Timestamp: 1756045588 Timestamp [UCT]: 2025-08-24 14:26:28 Age [y:d:h:m:s]: 00:093:22:55:55
Block: 1353471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67092 RingCT/type: yes/0
Extra: 018334f4a53477f8c086227e9be821ca1c1ad578c46f37a2171f271562b046506a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab5194c8d2a5997028a8b35c3afe8d58b7592981845b5f4462e4134f3d068027 0.600000000000 1841446 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1353481, "vin": [ { "gen": { "height": 1353471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab5194c8d2a5997028a8b35c3afe8d58b7592981845b5f4462e4134f3d068027" } } ], "extra": [ 1, 131, 52, 244, 165, 52, 119, 248, 192, 134, 34, 126, 155, 232, 33, 202, 28, 26, 213, 120, 196, 111, 55, 162, 23, 31, 39, 21, 98, 176, 70, 80, 106, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8