Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df49286180579f3a80a1fd82a21a36956b8b0e60fbed5f6743dc2e64079d8770

Tx prefix hash: a89b8c6f659a8e8c7ac0846219b606bf3e5150f60bc62980500b79fa8b4c2ce0
Tx public key: c93de5d946982bb0d7b13330804ae07379a5d5b155642c7e2aabdbe8bf743ec2
Timestamp: 1608649939 Timestamp [UCT]: 2020-12-22 15:12:19 Age [y:d:h:m:s]: 04:141:22:54:03
Block: 167156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114200 RingCT/type: yes/0
Extra: 01c93de5d946982bb0d7b13330804ae07379a5d5b155642c7e2aabdbe8bf743ec20211000003794ea414e5000000000000000000

1 output(s) for total of 171.456393978000 dcy

stealth address amount amount idx
00: 532d537e487cc768642f3424dff5957a43998303109a6a19bb0f73ee2f9b2991 171.456393978000 307669 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": 167166, "vin": [ { "gen": { "height": 167156 } } ], "vout": [ { "amount": 171456393978, "target": { "key": "532d537e487cc768642f3424dff5957a43998303109a6a19bb0f73ee2f9b2991" } } ], "extra": [ 1, 201, 61, 229, 217, 70, 152, 43, 176, 215, 177, 51, 48, 128, 74, 224, 115, 121, 165, 213, 177, 85, 100, 44, 126, 42, 171, 219, 232, 191, 116, 62, 194, 2, 17, 0, 0, 3, 121, 78, 164, 20, 229, 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