Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2456b4df9aea9b6a5f376c90299dba74279185a3e51b1627211b8260d09563b

Tx prefix hash: 345b0564c3e2c4d55905552f64d8d1686fc7a7e507e52596567450968e67738b
Tx public key: 9715d1623ba9090a6acaab6e3d944ce4629180ca7cd17ae9369d02b0546f7b29
Timestamp: 1701238519 Timestamp [UCT]: 2023-11-29 06:15:19 Age [y:d:h:m:s]: 01:052:03:07:52
Block: 902009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298612 RingCT/type: yes/0
Extra: 019715d1623ba9090a6acaab6e3d944ce4629180ca7cd17ae9369d02b0546f7b290211000000024b8f5122000000000000000000

1 output(s) for total of 0.629897264000 dcy

stealth address amount amount idx
00: fd91abfcb6f3455acf4e210f13f39207c934cc9c663d1450471335d9c2a39e65 0.629897264000 1358612 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": 902019, "vin": [ { "gen": { "height": 902009 } } ], "vout": [ { "amount": 629897264, "target": { "key": "fd91abfcb6f3455acf4e210f13f39207c934cc9c663d1450471335d9c2a39e65" } } ], "extra": [ 1, 151, 21, 209, 98, 59, 169, 9, 10, 106, 202, 171, 110, 61, 148, 76, 228, 98, 145, 128, 202, 124, 209, 122, 233, 54, 157, 2, 176, 84, 111, 123, 41, 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