Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b77bf4af5d7994d83b95aa81fe805f73faeaff9070692157340f79d17ee9ceb0

Tx prefix hash: ebba67eca224a343ff928ab22c2a8831cfb6f2e485ddfcbbf2e003165faf15a7
Tx public key: 20c52c285b4e4ea115882d1c0089566eb4a7f58e07090f0a4747db2041dfd856
Timestamp: 1737249462 Timestamp [UTC]: 2025-01-19 01:17:42 Age [y:d:h:m:s]: 01:025:10:10:06
Block: 1200379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276519 RingCT/type: yes/0
Extra: 0120c52c285b4e4ea115882d1c0089566eb4a7f58e07090f0a4747db2041dfd856021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cedf574efc4d1c83853939f95820221a4b8ca80b69d5433357c64b2ffeb02e80 0.000600000000 1687022 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 dinastycoin-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": 1200389, "vin": [ { "gen": { "height": 1200379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cedf574efc4d1c83853939f95820221a4b8ca80b69d5433357c64b2ffeb02e80" } } ], "extra": [ 1, 32, 197, 44, 40, 91, 78, 78, 161, 21, 136, 45, 28, 0, 137, 86, 110, 180, 167, 245, 142, 7, 9, 15, 10, 71, 71, 219, 32, 65, 223, 216, 86, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369