Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199c8a3616adaee2ae36544b56ee70e5b61a26890a91f59fcaa28e50bae63934

Tx prefix hash: f60170b97f455922e754f46d9fd744e97da75558f61c7bfd1ec0e8a87c09021f
Tx public key: 1d74e5c81f09e165269531157405751dbf48453c7be2fa9f37aaa28f54ee2a1c
Timestamp: 1726513838 Timestamp [UCT]: 2024-09-16 19:10:38 Age [y:d:h:m:s]: 00:181:17:19:54
Block: 1111557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129712 RingCT/type: yes/0
Extra: 011d74e5c81f09e165269531157405751dbf48453c7be2fa9f37aaa28f54ee2a1c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808c32d6d380f4fb312bdb802d923086d3320a8806bc71b9cb1e5b0b65a224d4 0.600000000000 1590562 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": 1111567, "vin": [ { "gen": { "height": 1111557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808c32d6d380f4fb312bdb802d923086d3320a8806bc71b9cb1e5b0b65a224d4" } } ], "extra": [ 1, 29, 116, 229, 200, 31, 9, 225, 101, 38, 149, 49, 21, 116, 5, 117, 29, 191, 72, 69, 60, 123, 226, 250, 159, 55, 170, 162, 143, 84, 238, 42, 28, 2, 17, 0, 0, 0, 3, 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