Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6408b54c2fbfa1e7c728db111029f88d026eb4bdf933ef896757c42d977e6ac

Tx prefix hash: c9973a61171295ee30b7a8ea5c8cfa69277b4a51402c070566c6de3a1c76dbe7
Tx public key: c8cf6e9ff8f936a68157ba3b79253d886b9d31a3d3a4d9740085e755eea1f8f5
Timestamp: 1746316014 Timestamp [UCT]: 2025-05-03 23:46:54 Age [y:d:h:m:s]: 00:197:20:33:23
Block: 1275200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139125 RingCT/type: yes/0
Extra: 01c8cf6e9ff8f936a68157ba3b79253d886b9d31a3d3a4d9740085e755eea1f8f50211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1341bda20d65196bbd685154004d8ad90b6bf3c8dee8ae9c1f8c0ccecaa71df7 0.600000000000 1762505 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": 1275210, "vin": [ { "gen": { "height": 1275200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1341bda20d65196bbd685154004d8ad90b6bf3c8dee8ae9c1f8c0ccecaa71df7" } } ], "extra": [ 1, 200, 207, 110, 159, 248, 249, 54, 166, 129, 87, 186, 59, 121, 37, 61, 136, 107, 157, 49, 163, 211, 164, 217, 116, 0, 133, 231, 85, 238, 161, 248, 245, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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