Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea731fe779c02d1ad9ed17afbc7ae049fd51b48ca222f75b38de50a9dfc9946c

Tx prefix hash: 663c69d9bcac52492010ed1d5cacd27ba71d642627062eecc2b4c9071d7a3085
Tx public key: d1e0d23dda82211ef8f7f88cd3808901a8ec094073ba3e7c38937111c1f0c12c
Timestamp: 1734321567 Timestamp [UCT]: 2024-12-16 03:59:27 Age [y:d:h:m:s]: 00:094:22:03:12
Block: 1176196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67618 RingCT/type: yes/0
Extra: 01d1e0d23dda82211ef8f7f88cd3808901a8ec094073ba3e7c38937111c1f0c12c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dad28b43c9c6ec80e0dd6e6f20324583440ef94b2f6d46dc094b90cbdc946c0 0.600000000000 1662527 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": 1176206, "vin": [ { "gen": { "height": 1176196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dad28b43c9c6ec80e0dd6e6f20324583440ef94b2f6d46dc094b90cbdc946c0" } } ], "extra": [ 1, 209, 224, 210, 61, 218, 130, 33, 30, 248, 247, 248, 140, 211, 128, 137, 1, 168, 236, 9, 64, 115, 186, 62, 124, 56, 147, 113, 17, 193, 240, 193, 44, 2, 17, 0, 0, 0, 4, 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