Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de2e8331fc1c81db4089f68d5b7737747d0a66828e196798079677156283cca7

Tx prefix hash: 9e5ca50aba218a086eaf1c4b10ce13c4b9a2dd8bea07ef844f81ec991f96ebd3
Tx public key: 7b1b38d848c9fc53d47a3a52de8f0567ba7460ddbd526656f8f665c66c78c4b9
Timestamp: 1734446397 Timestamp [UCT]: 2024-12-17 14:39:57 Age [y:d:h:m:s]: 00:121:04:42:57
Block: 1177238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86378 RingCT/type: yes/0
Extra: 017b1b38d848c9fc53d47a3a52de8f0567ba7460ddbd526656f8f665c66c78c4b90211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974ab61fbaeab38affd01762a31fdf80f9ea9a840d79af99c5b8af71b5083fe5 0.600000000000 1663603 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": 1177248, "vin": [ { "gen": { "height": 1177238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974ab61fbaeab38affd01762a31fdf80f9ea9a840d79af99c5b8af71b5083fe5" } } ], "extra": [ 1, 123, 27, 56, 216, 72, 201, 252, 83, 212, 122, 58, 82, 222, 143, 5, 103, 186, 116, 96, 221, 189, 82, 102, 86, 248, 246, 101, 198, 108, 120, 196, 185, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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