Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f19c5e9f0bed657e1a926fa4f64960ffe53121f3bb108f8c897d84620aa060

Tx prefix hash: 43343f300723be67e3fc8ff8c13471c8b358ce3f9cd0f033622741bb83cb3a56
Tx public key: 636fa25e059cbbb3650ae93b0e7cd13eb91b9142fb2f1284b8bbc3264d0a9d0a
Timestamp: 1624060233 Timestamp [UCT]: 2021-06-18 23:50:33 Age [y:d:h:m:s]: 03:231:02:58:41
Block: 280033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931596 RingCT/type: yes/0
Extra: 01636fa25e059cbbb3650ae93b0e7cd13eb91b9142fb2f1284b8bbc3264d0a9d0a0211000000126e2c823c000000000000000000

1 output(s) for total of 72.466109033000 dcy

stealth address amount amount idx
00: 12b775e0ec5aa0ba6eba60bd61c28c48b44c847bef655860e9405c0580af4e2f 72.466109033000 586392 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": 280043, "vin": [ { "gen": { "height": 280033 } } ], "vout": [ { "amount": 72466109033, "target": { "key": "12b775e0ec5aa0ba6eba60bd61c28c48b44c847bef655860e9405c0580af4e2f" } } ], "extra": [ 1, 99, 111, 162, 94, 5, 156, 187, 179, 101, 10, 233, 59, 14, 124, 209, 62, 185, 27, 145, 66, 251, 47, 18, 132, 184, 187, 195, 38, 77, 10, 157, 10, 2, 17, 0, 0, 0, 18, 110, 44, 130, 60, 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