Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76912a1b451eb29d217a4c3a94d13b9221c38ed570c941b319c9ac0d0cb92150

Tx prefix hash: 6943097dc57c93d6d1d8b2220ebe82119ba4fb2f5252e8a55ce58cedfe152699
Tx public key: 8f1da592896136ec3b694570640d5b5060441c83a33051dd1418b8a64d58095e
Timestamp: 1583077377 Timestamp [UCT]: 2020-03-01 15:42:57 Age [y:d:h:m:s]: 04:299:17:13:08
Block: 74509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108259 RingCT/type: yes/0
Extra: 018f1da592896136ec3b694570640d5b5060441c83a33051dd1418b8a64d58095e0211000001ed7adf42d3000000000000000000

1 output(s) for total of 347.633443873000 dcy

stealth address amount amount idx
00: 34579b1779419650f3e9e42ee5f176c551453bd069934a01d032777522b0d379 347.633443873000 137882 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": 74519, "vin": [ { "gen": { "height": 74509 } } ], "vout": [ { "amount": 347633443873, "target": { "key": "34579b1779419650f3e9e42ee5f176c551453bd069934a01d032777522b0d379" } } ], "extra": [ 1, 143, 29, 165, 146, 137, 97, 54, 236, 59, 105, 69, 112, 100, 13, 91, 80, 96, 68, 28, 131, 163, 48, 81, 221, 20, 24, 184, 166, 77, 88, 9, 94, 2, 17, 0, 0, 1, 237, 122, 223, 66, 211, 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