Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29e7d616e9668cd57c5811e6523f5e047ad1440f4f534f24acf4820c992cc29

Tx prefix hash: 7dc2141fd23328477eb420e5e979ec0cd2c16423580b9a4fa272471cfd82c585
Tx public key: 7ecc40580dec17ce7400bf0c118f27b7a7c5d5fae8fee12930f7f88bf86da8ec
Timestamp: 1733725291 Timestamp [UCT]: 2024-12-09 06:21:31 Age [y:d:h:m:s]: 00:328:06:31:18
Block: 1171247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232116 RingCT/type: yes/0
Extra: 017ecc40580dec17ce7400bf0c118f27b7a7c5d5fae8fee12930f7f88bf86da8ec0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aff70682e272c3af0c73268d25351785244c1462705195e953b82934a34d3fd 0.600000000000 1656986 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": 1171257, "vin": [ { "gen": { "height": 1171247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aff70682e272c3af0c73268d25351785244c1462705195e953b82934a34d3fd" } } ], "extra": [ 1, 126, 204, 64, 88, 13, 236, 23, 206, 116, 0, 191, 12, 17, 143, 39, 183, 167, 197, 213, 250, 232, 254, 225, 41, 48, 247, 248, 139, 248, 109, 168, 236, 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