Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6ffc4102dbcdf8ee7553812af3854c8296da96dd92f2d2697e62f78db875640

Tx prefix hash: af546dddfcb35c2858ae612435fd5fe0a31e668a363887d3342e71784353d2af
Tx public key: 5471bfd2eec12d7d9ceb5e451b1557e0cba99f5d252517bdcb15fd1544d0e1f2
Timestamp: 1723766765 Timestamp [UCT]: 2024-08-16 00:06:05 Age [y:d:h:m:s]: 01:144:11:44:16
Block: 1088788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361803 RingCT/type: yes/0
Extra: 015471bfd2eec12d7d9ceb5e451b1557e0cba99f5d252517bdcb15fd1544d0e1f2021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 685989f852e7679bd9cf2b6d4b2e154d83fd518fcb29105377440edc43093db4 0.600000000000 1563407 of 15

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": 1088798, "vin": [ { "gen": { "height": 1088788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "685989f852e7679bd9cf2b6d4b2e154d83fd518fcb29105377440edc43093db4" } } ], "extra": [ 1, 84, 113, 191, 210, 238, 193, 45, 125, 156, 235, 94, 69, 27, 21, 87, 224, 203, 169, 159, 93, 37, 37, 23, 189, 203, 21, 253, 21, 68, 208, 225, 242, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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