Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b332be7d1b3b37cdf3f08d1951e1cec712417d562528876efb033270c97cf72

Tx prefix hash: cb3fb839029bb2cd67fb052908cd8774bdcd3b3794100bf77148c2cd44fc1fe5
Tx public key: 0d28e81fd66280423c8d12383cd99eccdbfc4b3525c8cb181dfe3cea06e39b4e
Timestamp: 1646600674 Timestamp [UCT]: 2022-03-06 21:04:34 Age [y:d:h:m:s]: 02:343:18:31:22
Block: 452803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 764951 RingCT/type: yes/0
Extra: 010d28e81fd66280423c8d12383cd99eccdbfc4b3525c8cb181dfe3cea06e39b4e0211000000055eb576c5000000000000000000

1 output(s) for total of 19.394383018000 dcy

stealth address amount amount idx
00: 333cc5ba472506b7b4a8129a8c97c76624d780a0bf0e9b2c828baf07469fe27d 19.394383018000 868176 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": 452813, "vin": [ { "gen": { "height": 452803 } } ], "vout": [ { "amount": 19394383018, "target": { "key": "333cc5ba472506b7b4a8129a8c97c76624d780a0bf0e9b2c828baf07469fe27d" } } ], "extra": [ 1, 13, 40, 232, 31, 214, 98, 128, 66, 60, 141, 18, 56, 60, 217, 158, 204, 219, 252, 75, 53, 37, 200, 203, 24, 29, 254, 60, 234, 6, 227, 155, 78, 2, 17, 0, 0, 0, 5, 94, 181, 118, 197, 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