Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 700bb0018526d803bff0b8c73f2dfdcb200b70bb9cb63f0437d861b7f812148f

Tx prefix hash: ccfc2db743bfb5d1348881c3ae8efdadd37d6d5587996dba248a53a5bc4ed091
Tx public key: af57fd3ddd132139a45af40b112fac44d5756cfba0de6b6bb1dd9f85cba838a4
Timestamp: 1577530411 Timestamp [UCT]: 2019-12-28 10:53:31 Age [y:d:h:m:s]: 05:001:22:44:27
Block: 33409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151514 RingCT/type: yes/0
Extra: 01af57fd3ddd132139a45af40b112fac44d5756cfba0de6b6bb1dd9f85cba838a40211000000034ac5aa02000000000000000000

1 output(s) for total of 475.666943943000 dcy

stealth address amount amount idx
00: e64a2c8245a3b867274a4d5f47bb701275356401ca5a41db6dd6ab4c5d882518 475.666943943000 55929 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": 33419, "vin": [ { "gen": { "height": 33409 } } ], "vout": [ { "amount": 475666943943, "target": { "key": "e64a2c8245a3b867274a4d5f47bb701275356401ca5a41db6dd6ab4c5d882518" } } ], "extra": [ 1, 175, 87, 253, 61, 221, 19, 33, 57, 164, 90, 244, 11, 17, 47, 172, 68, 213, 117, 108, 251, 160, 222, 107, 107, 177, 221, 159, 133, 203, 168, 56, 164, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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