Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2eb8d85f0a7ef25923914a518fb3878a5e6fb1d26df0e487c1732830c835d77

Tx prefix hash: bd017e9209896d15cf270904440e048d5de66bbdcb893b7aa583bf30e700dc6b
Tx public key: 02fe1d3951ae1b1a8c1cb7675bd9e79131d09f1a3b880cb4c5e89eb9d1f21cfe
Timestamp: 1675637725 Timestamp [UCT]: 2023-02-05 22:55:25 Age [y:d:h:m:s]: 02:063:21:16:36
Block: 690653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567269 RingCT/type: yes/0
Extra: 0102fe1d3951ae1b1a8c1cb7675bd9e79131d09f1a3b880cb4c5e89eb9d1f21cfe0211000000035029cbac000000000000000000

1 output(s) for total of 3.159219739000 dcy

stealth address amount amount idx
00: bf5f25c43c2302e0905091597dcf55cb075482a1c6f20db77f858404f25b1748 3.159219739000 1133387 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": 690663, "vin": [ { "gen": { "height": 690653 } } ], "vout": [ { "amount": 3159219739, "target": { "key": "bf5f25c43c2302e0905091597dcf55cb075482a1c6f20db77f858404f25b1748" } } ], "extra": [ 1, 2, 254, 29, 57, 81, 174, 27, 26, 140, 28, 183, 103, 91, 217, 231, 145, 49, 208, 159, 26, 59, 136, 12, 180, 197, 232, 158, 185, 209, 242, 28, 254, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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