Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e1b03f1c21a48d68b5f88e1e2b8a5af70f5fad7697104b74ba625547c7b7101

Tx prefix hash: 012e4859dbd84a145e589d78817154f1906e23943dc2c78e325aee34221a2632
Tx public key: 4881114c110f51562d63c2eed931e76053531ddc07095581e797e23e4d25e7b4
Timestamp: 1740071384 Timestamp [UTC]: 2025-02-20 17:09:44 Age [y:d:h:m:s]: 00:359:15:37:53
Block: 1223488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254725 RingCT/type: yes/0
Extra: 014881114c110f51562d63c2eed931e76053531ddc07095581e797e23e4d25e7b40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a825dfed8f5415bdde2a22342cfb530928e54d20a103789ec6860a4d17264f25 0.000600000000 1710345 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": 1223498, "vin": [ { "gen": { "height": 1223488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a825dfed8f5415bdde2a22342cfb530928e54d20a103789ec6860a4d17264f25" } } ], "extra": [ 1, 72, 129, 17, 76, 17, 15, 81, 86, 45, 99, 194, 238, 217, 49, 231, 96, 83, 83, 29, 220, 7, 9, 85, 129, 231, 151, 226, 62, 77, 37, 231, 180, 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): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369