Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8874200416c5f51984cb714009925be85b308ecc3bd2e3a58ff2a96c263ba988

Tx prefix hash: 9868e78abc5d6999059e0df1dad49972e776220adb8a2f1e62a8171ebd74d1d2
Tx public key: e8b9655c9147797551c92b6f53a1d20cb0bada5ed4cb2d924854fe8fba48ace7
Timestamp: 1703014300 Timestamp [UCT]: 2023-12-19 19:31:40 Age [y:d:h:m:s]: 01:349:17:34:24
Block: 916742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508844 RingCT/type: yes/0
Extra: 01e8b9655c9147797551c92b6f53a1d20cb0bada5ed4cb2d924854fe8fba48ace702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6eb529b22187ce6dd64fef4e1f3f58215c4513f58275691b57a8501bef12a93 0.600000000000 1374302 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": 916752, "vin": [ { "gen": { "height": 916742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6eb529b22187ce6dd64fef4e1f3f58215c4513f58275691b57a8501bef12a93" } } ], "extra": [ 1, 232, 185, 101, 92, 145, 71, 121, 117, 81, 201, 43, 111, 83, 161, 210, 12, 176, 186, 218, 94, 212, 203, 45, 146, 72, 84, 254, 143, 186, 72, 172, 231, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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