Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a7006bc00d8026d147a97317baada3001dedf28c7def34b59d1a0716769867

Tx prefix hash: f438a24a7be3d733f6673ef2d5660d38ab73e2946c3a487c94263c0a529f0cf7
Tx public key: d1f7a17692efc8bb4a729125d5d9d8d9d17a5234d059254aff4b1db572da4593
Timestamp: 1715338001 Timestamp [UCT]: 2024-05-10 10:46:41 Age [y:d:h:m:s]: 00:328:15:26:46
Block: 1018913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234895 RingCT/type: yes/0
Extra: 01d1f7a17692efc8bb4a729125d5d9d8d9d17a5234d059254aff4b1db572da45930211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a8f00861c1d779fdbc33afc6d70cb3ae458ddcc5a434dd32f3c47714a0e3bc7 0.600000000000 1482730 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": 1018923, "vin": [ { "gen": { "height": 1018913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a8f00861c1d779fdbc33afc6d70cb3ae458ddcc5a434dd32f3c47714a0e3bc7" } } ], "extra": [ 1, 209, 247, 161, 118, 146, 239, 200, 187, 74, 114, 145, 37, 213, 217, 216, 217, 209, 122, 82, 52, 208, 89, 37, 74, 255, 75, 29, 181, 114, 218, 69, 147, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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