Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec3daef3770756539fa14606919178fde00703a0e8486676b250ecdaf7280777

Tx prefix hash: f361dee2d8c55e0a5049c40f2a4b91f2d6a230f3c65989a1a7c4a1e306f4ff70
Tx public key: 32251968ccf7e0abf6f386e6fe03932c81ad54501ec0f9081c67eb5a2f2d989d
Timestamp: 1581570626 Timestamp [UCT]: 2020-02-13 05:10:26 Age [y:d:h:m:s]: 04:291:04:18:58
Block: 63917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100260 RingCT/type: yes/0
Extra: 0132251968ccf7e0abf6f386e6fe03932c81ad54501ec0f9081c67eb5a2f2d989d0211000000020aca7173000000000000000000

1 output(s) for total of 376.892294431000 dcy

stealth address amount amount idx
00: d3d395e23a088952cdfb0ec17be61fb8e94c74c20d1df15abffa9ab00b14d023 376.892294431000 117817 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": 63927, "vin": [ { "gen": { "height": 63917 } } ], "vout": [ { "amount": 376892294431, "target": { "key": "d3d395e23a088952cdfb0ec17be61fb8e94c74c20d1df15abffa9ab00b14d023" } } ], "extra": [ 1, 50, 37, 25, 104, 204, 247, 224, 171, 246, 243, 134, 230, 254, 3, 147, 44, 129, 173, 84, 80, 30, 192, 249, 8, 28, 103, 235, 90, 47, 45, 152, 157, 2, 17, 0, 0, 0, 2, 10, 202, 113, 115, 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