Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a28c4da0c8268b3cded2e93b48f2892158b8ddc1ed8a1309083af116a3eeafd

Tx prefix hash: ee62d890c5b94ed924496779edf0959c95915ffbbb6c4a58f7b49cf03e4aa9a1
Tx public key: 123d4e569b0604c1fad6a19f5159d0034fe832f63086f5534d0efb6387fcc89b
Timestamp: 1728154654 Timestamp [UCT]: 2024-10-05 18:57:34 Age [y:d:h:m:s]: 00:174:20:11:08
Block: 1125160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124752 RingCT/type: yes/0
Extra: 01123d4e569b0604c1fad6a19f5159d0034fe832f63086f5534d0efb6387fcc89b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad7da76c5543187fdd13e5ab85a8d0b6fc84f36677d78fbd5f40715840799721 0.600000000000 1607837 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": 1125170, "vin": [ { "gen": { "height": 1125160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad7da76c5543187fdd13e5ab85a8d0b6fc84f36677d78fbd5f40715840799721" } } ], "extra": [ 1, 18, 61, 78, 86, 155, 6, 4, 193, 250, 214, 161, 159, 81, 89, 208, 3, 79, 232, 50, 246, 48, 134, 245, 83, 77, 14, 251, 99, 135, 252, 200, 155, 2, 17, 0, 0, 0, 2, 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