Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970384cb89358efd27bfceb3c64f74f9b53c7c8648fa32ac01d1408aeae2cfb2

Tx prefix hash: 6781b9f457ff104db98d6558de4568f553dafe2e9d4ecc9e2128b3fa3eb34460
Tx public key: d0aa4fb1fb216c9fd4c189e739cdce2bf2afe2bc4e2cc3e41a9fd7e455444842
Timestamp: 1764106337 Timestamp [UTC]: 2025-11-25 21:32:17 Age [y:d:h:m:s]: 00:353:08:37:32
Block: 1420092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257849 RingCT/type: yes/0
Extra: 01d0aa4fb1fb216c9fd4c189e739cdce2bf2afe2bc4e2cc3e41a9fd7e455444842021100000001defb8f18000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 77fd3c0eb7c43b02f3de51f15165b94693605fa59cc828d0221d1d8c51cc398b 0.000600000000 1908633 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": 1420102, "vin": [ { "gen": { "height": 1420092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77fd3c0eb7c43b02f3de51f15165b94693605fa59cc828d0221d1d8c51cc398b" } } ], "extra": [ 1, 208, 170, 79, 177, 251, 33, 108, 159, 212, 193, 137, 231, 57, 205, 206, 43, 242, 175, 226, 188, 78, 44, 195, 228, 26, 159, 215, 228, 85, 68, 72, 66, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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: