Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2573e2a7bdaecbd5b7abaf74f660138b65d1fb5274124a52f3c6e0f8f8b73ed

Tx prefix hash: 7cdf9a0c35fd35fb7876dd3afc23ce8a71593b4ddf224d98bbb90e5956740b61
Tx public key: 4d0fc6654560abfdef1913b1f46b17561d8d30256aefbbec2c24df2bb3ff2f72
Timestamp: 1700860169 Timestamp [UCT]: 2023-11-24 21:09:29 Age [y:d:h:m:s]: 01:097:16:40:08
Block: 898884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330951 RingCT/type: yes/0
Extra: 014d0fc6654560abfdef1913b1f46b17561d8d30256aefbbec2c24df2bb3ff2f72021100000003faf35c9c000000000000000000

1 output(s) for total of 0.645095702000 dcy

stealth address amount amount idx
00: 6a9f76f28340f23a19ee77a53c7d4d82f2428964d856035e819c93f9c629dbe0 0.645095702000 1355321 of 0

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": 898894, "vin": [ { "gen": { "height": 898884 } } ], "vout": [ { "amount": 645095702, "target": { "key": "6a9f76f28340f23a19ee77a53c7d4d82f2428964d856035e819c93f9c629dbe0" } } ], "extra": [ 1, 77, 15, 198, 101, 69, 96, 171, 253, 239, 25, 19, 177, 244, 107, 23, 86, 29, 141, 48, 37, 106, 239, 187, 236, 44, 36, 223, 43, 179, 255, 47, 114, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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