Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c16b09977a23c8b1dc2b563a130f60a57c1237d46d5ae653712ed13afd2dbbc

Tx prefix hash: 9bf159c68e324f50d99ffb954b60f5ac27461679c56af4312ead3384003b4f87
Tx public key: b17a60318a0da2522e838334ba0e43e341369f4a0949e3a04100453e9e534f39
Timestamp: 1763444574 Timestamp [UCT]: 2025-11-18 05:42:54 Age [y:d:h:m:s]: 00:065:12:23:55
Block: 1414600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46781 RingCT/type: yes/0
Extra: 01b17a60318a0da2522e838334ba0e43e341369f4a0949e3a04100453e9e534f3902110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61fd79c805a05cb1b85ad1854b0489a3a75dc1bbdfa4d6559b69d11fd35f7666 0.600000000000 1903091 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": 1414610, "vin": [ { "gen": { "height": 1414600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61fd79c805a05cb1b85ad1854b0489a3a75dc1bbdfa4d6559b69d11fd35f7666" } } ], "extra": [ 1, 177, 122, 96, 49, 138, 13, 162, 82, 46, 131, 131, 52, 186, 14, 67, 227, 65, 54, 159, 74, 9, 73, 227, 160, 65, 0, 69, 62, 158, 83, 79, 57, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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