Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8936c92c2102b03d41c2ecc955ae45bd34e6a356fe9d90d44c82c21a3e3cb3c

Tx prefix hash: c085610415e8563ab3eedda5ce861e1c558d34f5663aa2cd17a7f7cfff8402e0
Tx public key: 29e57c960f013ebde73a5a96e5d3364513c7c6c8037344dab2ef84ce42201c0d
Timestamp: 1730500680 Timestamp [UCT]: 2024-11-01 22:38:00 Age [y:d:h:m:s]: 00:144:00:23:31
Block: 1144520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102757 RingCT/type: yes/0
Extra: 0129e57c960f013ebde73a5a96e5d3364513c7c6c8037344dab2ef84ce42201c0d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19537322e23f53ff1f626a28dc70853cf68a8983f7a4cbda908400aea0ac77a1 0.600000000000 1628761 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": 1144530, "vin": [ { "gen": { "height": 1144520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19537322e23f53ff1f626a28dc70853cf68a8983f7a4cbda908400aea0ac77a1" } } ], "extra": [ 1, 41, 229, 124, 150, 15, 1, 62, 189, 231, 58, 90, 150, 229, 211, 54, 69, 19, 199, 198, 200, 3, 115, 68, 218, 178, 239, 132, 206, 66, 32, 28, 13, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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