Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f45da4a46e4e07ddec6d1cd899123373835bd3d8eae03f050e8c833395175f75

Tx prefix hash: ee2d8062d590072584e2cb0b0ac5b46c9616ba7f538bb7419c43ca4d5bdbfbf1
Tx public key: c40a3d0b740224c074463e7dfde8abe63e7c48f5a300f479637fbbfa289c8204
Timestamp: 1713658240 Timestamp [UCT]: 2024-04-21 00:10:40 Age [y:d:h:m:s]: 01:197:09:05:14
Block: 1004966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399727 RingCT/type: yes/0
Extra: 01c40a3d0b740224c074463e7dfde8abe63e7c48f5a300f479637fbbfa289c82040211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dcf473d15548d3d9211c79809ff64b15e10169a509ffbd3a0adb759ef2afdc1 0.600000000000 1465540 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": 1004976, "vin": [ { "gen": { "height": 1004966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dcf473d15548d3d9211c79809ff64b15e10169a509ffbd3a0adb759ef2afdc1" } } ], "extra": [ 1, 196, 10, 61, 11, 116, 2, 36, 192, 116, 70, 62, 125, 253, 232, 171, 230, 62, 124, 72, 245, 163, 0, 244, 121, 99, 127, 187, 250, 40, 156, 130, 4, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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