Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c1a77459bfdddf2ae7e0abe9d3fa8b76804e4e9f671f5efd09dfa8940a1be6

Tx prefix hash: f81b7d0eca27ed5c2bf452fe47f392819689bc87fcaf7fa99f11a8037fb53b52
Tx public key: ba1f72c354f7d5120a658e3208ffefaef97a10d4c4693178e4d7fc1c95470a0c
Timestamp: 1758778031 Timestamp [UTC]: 2025-09-25 05:27:11 Age [y:d:h:m:s]: 01:051:08:42:33
Block: 1375925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303019 RingCT/type: yes/0
Extra: 01ba1f72c354f7d5120a658e3208ffefaef97a10d4c4693178e4d7fc1c95470a0c021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 81c1ff02c6720c75940679fc4ae1a582ec2d2cc8e98fae41262f7bc2db9835fd 0.000600000000 1864016 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": 1375935, "vin": [ { "gen": { "height": 1375925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81c1ff02c6720c75940679fc4ae1a582ec2d2cc8e98fae41262f7bc2db9835fd" } } ], "extra": [ 1, 186, 31, 114, 195, 84, 247, 213, 18, 10, 101, 142, 50, 8, 255, 239, 174, 249, 122, 16, 212, 196, 105, 49, 120, 228, 215, 252, 28, 149, 71, 10, 12, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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) | monero version: