Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 572ccaf45efc8136f9c039a169db6038e2574e61ae7d5bfd4b1ebd985ca96a98

Tx prefix hash: decf9784379144076e4368d9b17b2a58014ec40be7c686f472ca021e401b45c2
Tx public key: 830a934a3142bf8e600ed19a1b5be141f6df1b74fcc55e41e9a275cb8fe78db0
Timestamp: 1718580063 Timestamp [UCT]: 2024-06-16 23:21:03 Age [y:d:h:m:s]: 00:291:07:13:43
Block: 1045801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208147 RingCT/type: yes/0
Extra: 01830a934a3142bf8e600ed19a1b5be141f6df1b74fcc55e41e9a275cb8fe78db002110000000556e59e1d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8bf5a111795047deba1b4ac3cea8c93efba507db064a77d48540b033b500ccd 0.600000000000 1515476 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": 1045811, "vin": [ { "gen": { "height": 1045801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8bf5a111795047deba1b4ac3cea8c93efba507db064a77d48540b033b500ccd" } } ], "extra": [ 1, 131, 10, 147, 74, 49, 66, 191, 142, 96, 14, 209, 154, 27, 91, 225, 65, 246, 223, 27, 116, 252, 197, 94, 65, 233, 162, 117, 203, 143, 231, 141, 176, 2, 17, 0, 0, 0, 5, 86, 229, 158, 29, 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