Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4384f89094970ad05cff649c8b81edafaed313ab1de569624a07d9582cc91da

Tx prefix hash: 31647b1fdb880401f01820e136d2ca02dcf66fd913f857ca09d9a363c05553bb
Tx public key: e803fb93e919f72833591b4ebd8b8e5b1a9e9aa7af3628eb841d388675be9d4f
Timestamp: 1715198119 Timestamp [UCT]: 2024-05-08 19:55:19 Age [y:d:h:m:s]: 00:293:01:33:09
Block: 1017756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209453 RingCT/type: yes/0
Extra: 01e803fb93e919f72833591b4ebd8b8e5b1a9e9aa7af3628eb841d388675be9d4f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9cd621977b8c995ff2d18ab6b24dd7bdbe0e93236a0a65d1104409b21135548 0.600000000000 1481541 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": 1017766, "vin": [ { "gen": { "height": 1017756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9cd621977b8c995ff2d18ab6b24dd7bdbe0e93236a0a65d1104409b21135548" } } ], "extra": [ 1, 232, 3, 251, 147, 233, 25, 247, 40, 51, 89, 27, 78, 189, 139, 142, 91, 26, 158, 154, 167, 175, 54, 40, 235, 132, 29, 56, 134, 117, 190, 157, 79, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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