Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee98399af191a2c62a6f0537119f12d254fc63b530d81697bd62ba0b931db1f6

Tx prefix hash: 162faf0ecdbe680562ef32cee0c7f8be738586c6009ebcfcd660f14fb6c08c94
Tx public key: ca4897b53e15a79f5304eb56268c8bee0ca7582eee533a54487a73abbe717a57
Timestamp: 1582056423 Timestamp [UCT]: 2020-02-18 20:07:03 Age [y:d:h:m:s]: 05:074:22:35:28
Block: 67725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206611 RingCT/type: yes/0
Extra: 01ca4897b53e15a79f5304eb56268c8bee0ca7582eee533a54487a73abbe717a57021100000071d81c26c0000000000000000000

1 output(s) for total of 366.100032999000 dcy

stealth address amount amount idx
00: 4fa79fb36502cd5528a78a3855ef89f0b4cead2b50ceb15b9b07dd36691c8a7d 366.100032999000 124734 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": 67735, "vin": [ { "gen": { "height": 67725 } } ], "vout": [ { "amount": 366100032999, "target": { "key": "4fa79fb36502cd5528a78a3855ef89f0b4cead2b50ceb15b9b07dd36691c8a7d" } } ], "extra": [ 1, 202, 72, 151, 181, 62, 21, 167, 159, 83, 4, 235, 86, 38, 140, 139, 238, 12, 167, 88, 46, 238, 83, 58, 84, 72, 122, 115, 171, 190, 113, 122, 87, 2, 17, 0, 0, 0, 113, 216, 28, 38, 192, 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