Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e54bb5fbbc2621ba369ec239a93b3aca13ab435927b8639811be9c9e712d315c

Tx prefix hash: 241b73e7db097702eb39b6e6727de42f62adece51e1e00f7d0111fa1d5dc69c2
Tx public key: ee4345b4a3fbed1c3e060b91a9dc74010e982d622a3c1395d9b6ae40528296db
Timestamp: 1703569710 Timestamp [UCT]: 2023-12-26 05:48:30 Age [y:d:h:m:s]: 00:325:06:02:48
Block: 921345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232880 RingCT/type: yes/0
Extra: 01ee4345b4a3fbed1c3e060b91a9dc74010e982d622a3c1395d9b6ae40528296db021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d97bafccc6f21ddecc23f1571f3cbb67fc12f8dd69405f155e35ed339870a16 0.600000000000 1379031 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": 921355, "vin": [ { "gen": { "height": 921345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d97bafccc6f21ddecc23f1571f3cbb67fc12f8dd69405f155e35ed339870a16" } } ], "extra": [ 1, 238, 67, 69, 180, 163, 251, 237, 28, 62, 6, 11, 145, 169, 220, 116, 1, 14, 152, 45, 98, 42, 60, 19, 149, 217, 182, 174, 64, 82, 130, 150, 219, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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