Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8424bf6ea58352049b8352aabe3915095947aedcdbb12b429878a09fc9810177

Tx prefix hash: 970e87b8ca851476ae2db91a231e3f1cdba892f6ff28794e747e41b6259025b8
Tx public key: 602e639343b8f816209dd1f6a084e05b99fe9062d74c1d1c9900df8db16f3fe2
Timestamp: 1722733841 Timestamp [UCT]: 2024-08-04 01:10:41 Age [y:d:h:m:s]: 00:233:10:28:24
Block: 1080220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166722 RingCT/type: yes/0
Extra: 01602e639343b8f816209dd1f6a084e05b99fe9062d74c1d1c9900df8db16f3fe2021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 376b0c0a0559a50f7f3fbc9d39ea9217fcd3c052db88539146e4c11b74d7f461 0.600000000000 1553493 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": 1080230, "vin": [ { "gen": { "height": 1080220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "376b0c0a0559a50f7f3fbc9d39ea9217fcd3c052db88539146e4c11b74d7f461" } } ], "extra": [ 1, 96, 46, 99, 147, 67, 184, 248, 22, 32, 157, 209, 246, 160, 132, 224, 91, 153, 254, 144, 98, 215, 76, 29, 28, 153, 0, 223, 141, 177, 111, 63, 226, 2, 17, 0, 0, 0, 5, 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