Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c4d56d14c8b9876810ad7b0551fc6a82f5d9483c241a5230e5087333bf214dc

Tx prefix hash: f8c739e5b64af003b11dbccca6ab1a36fad27241ab830a888d66cf6ec1ca5ff7
Tx public key: 78df4e223c6c5f575d47b4bb92df3ee7ed592417e329c67a78dc9c5a4e37b942
Timestamp: 1709856308 Timestamp [UCT]: 2024-03-08 00:05:08 Age [y:d:h:m:s]: 01:105:10:28:14
Block: 973476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336213 RingCT/type: yes/0
Extra: 0178df4e223c6c5f575d47b4bb92df3ee7ed592417e329c67a78dc9c5a4e37b94202110000000446812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d683c010afdb51cdbeff0c581e2e2d321435d00f73aa6d640cade3d3189d072a 0.600000000000 1433411 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": 973486, "vin": [ { "gen": { "height": 973476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d683c010afdb51cdbeff0c581e2e2d321435d00f73aa6d640cade3d3189d072a" } } ], "extra": [ 1, 120, 223, 78, 34, 60, 108, 95, 87, 93, 71, 180, 187, 146, 223, 62, 231, 237, 89, 36, 23, 227, 41, 198, 122, 120, 220, 156, 90, 78, 55, 185, 66, 2, 17, 0, 0, 0, 4, 70, 129, 43, 184, 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