Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cecbe214bf9505476ba734a2f539f21329c2aecc4d974cca8b83b9214944f79

Tx prefix hash: 8c24f6a4678e206fd5273090820ce272ae0edff6c830c306c270dbef68b13bba
Tx public key: 6a4e48e335542a5735aadf226540a4ab921c17b1f7a5299ccf9cb482f920a416
Timestamp: 1764134835 Timestamp [UCT]: 2025-11-26 05:27:15 Age [y:d:h:m:s]: 00:001:02:29:58
Block: 1420321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 798 RingCT/type: yes/0
Extra: 016a4e48e335542a5735aadf226540a4ab921c17b1f7a5299ccf9cb482f920a416021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af7af9ec70d6948fe24ac1bd12fb949cbc6dc8848123cc6599d1ce93fd165fe5 0.600000000000 1908864 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": 1420331, "vin": [ { "gen": { "height": 1420321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af7af9ec70d6948fe24ac1bd12fb949cbc6dc8848123cc6599d1ce93fd165fe5" } } ], "extra": [ 1, 106, 78, 72, 227, 53, 84, 42, 87, 53, 170, 223, 34, 101, 64, 164, 171, 146, 28, 23, 177, 247, 165, 41, 156, 207, 156, 180, 130, 249, 32, 164, 22, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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