Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60e01fa1f82c6d984853d53d2a40652ec207afb1e9f1941b4c894fa520f26fce

Tx prefix hash: 00948bae8eb97297bed31e5bf5f09189423412ca3b23b16aa89cd19eec1c94a6
Tx public key: 0065c4ac24d19abac1f68707077decf7d281e6a85e6cd874d0f16ade2bcf63a8
Timestamp: 1726245176 Timestamp [UCT]: 2024-09-13 16:32:56 Age [y:d:h:m:s]: 00:208:17:48:59
Block: 1109331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149019 RingCT/type: yes/0
Extra: 010065c4ac24d19abac1f68707077decf7d281e6a85e6cd874d0f16ade2bcf63a802110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7919b47e457a4534d025a6d0b42e18deb1b8d5e969f8cc8be79ecc85433cd46a 0.600000000000 1587544 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": 1109341, "vin": [ { "gen": { "height": 1109331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7919b47e457a4534d025a6d0b42e18deb1b8d5e969f8cc8be79ecc85433cd46a" } } ], "extra": [ 1, 0, 101, 196, 172, 36, 209, 154, 186, 193, 246, 135, 7, 7, 125, 236, 247, 210, 129, 230, 168, 94, 108, 216, 116, 208, 241, 106, 222, 43, 207, 99, 168, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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