Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ec5d95597a762709a959a6df5857acefd073dd9983eb611c955c10914d9369

Tx prefix hash: 8211a47b74f427d7e0392913a3257ab5a2e7a3c4085a17ec4bc5dd539f171b5f
Tx public key: 2138a598e06d02e356a3a1c65c8ac82cd0e82ad8b4c45c94020436b6a21353aa
Timestamp: 1699631295 Timestamp [UCT]: 2023-11-10 15:48:15 Age [y:d:h:m:s]: 01:072:18:10:24
Block: 888697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313362 RingCT/type: yes/0
Extra: 012138a598e06d02e356a3a1c65c8ac82cd0e82ad8b4c45c94020436b6a21353aa0211000000024b8f5122000000000000000000

1 output(s) for total of 0.697232983000 dcy

stealth address amount amount idx
00: 4394e0983a7d868d2875269dbcda93d9ec915692e20361a45abfb638daba472e 0.697232983000 1344652 of 0

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": 888707, "vin": [ { "gen": { "height": 888697 } } ], "vout": [ { "amount": 697232983, "target": { "key": "4394e0983a7d868d2875269dbcda93d9ec915692e20361a45abfb638daba472e" } } ], "extra": [ 1, 33, 56, 165, 152, 224, 109, 2, 227, 86, 163, 161, 198, 92, 138, 200, 44, 208, 232, 42, 216, 180, 196, 92, 148, 2, 4, 54, 182, 162, 19, 83, 170, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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