Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e468129394fc6dd18eddd038e20d0897a8c1376524e937f6574983d760b65d

Tx prefix hash: 982acca07c64e5c751a85aeaa68fd55aca9ffdbf3d7cedd6b05cfe63222bb19b
Tx public key: caa2b9ddccf15613619d0758b7a19981e9cd48e29cc8ddc7936c1913ab67b602
Timestamp: 1632293650 Timestamp [UCT]: 2021-09-22 06:54:10 Age [y:d:h:m:s]: 03:055:22:30:28
Block: 338633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816125 RingCT/type: yes/0
Extra: 01caa2b9ddccf15613619d0758b7a19981e9cd48e29cc8ddc7936c1913ab67b60202110000003ffdc024ec000000000000000000

1 output(s) for total of 46.341355394000 dcy

stealth address amount amount idx
00: e5582c6a6e3653ce293e70d899ae9be447a67c74fe8ddaa15870c41a402e1da3 46.341355394000 696846 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": 338643, "vin": [ { "gen": { "height": 338633 } } ], "vout": [ { "amount": 46341355394, "target": { "key": "e5582c6a6e3653ce293e70d899ae9be447a67c74fe8ddaa15870c41a402e1da3" } } ], "extra": [ 1, 202, 162, 185, 221, 204, 241, 86, 19, 97, 157, 7, 88, 183, 161, 153, 129, 233, 205, 72, 226, 156, 200, 221, 199, 147, 108, 25, 19, 171, 103, 182, 2, 2, 17, 0, 0, 0, 63, 253, 192, 36, 236, 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