Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd4df563c93aa2cb8f94de685be4b851114d11df6bed4993655c6bf6972aa15

Tx prefix hash: 666a6ecd38bb07c9aa4fab5359636c9ee11ff9993a7b70e146b4f1450a691b6d
Tx public key: c4d37cd54a697c7c6c5cabe3e83b3f7b24d97a7ec0f929d24d61cef6d27f88cb
Timestamp: 1789990133 Timestamp [UTC]: 2026-09-21 11:28:53 Age [y:d:h:m:s]: 00:049:08:16:24
Block: 1640321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 34134 RingCT/type: yes/0
Extra: 01c4d37cd54a697c7c6c5cabe3e83b3f7b24d97a7ec0f929d24d61cef6d27f88cb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9d2f8844b5b34d7847459e6d4a942c202b0a0ee1bafe049fc47c342825b97d23 0.000600000000 2130353 of 15 <a4>

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": 1640331, "vin": [ { "gen": { "height": 1640321 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9d2f8844b5b34d7847459e6d4a942c202b0a0ee1bafe049fc47c342825b97d23", "view_tag": "a4" } } } ], "extra": [ 1, 196, 211, 124, 213, 74, 105, 124, 124, 108, 92, 171, 227, 232, 59, 63, 123, 36, 217, 122, 126, 192, 249, 41, 210, 77, 97, 206, 246, 210, 127, 136, 203 ], "rct_signatures": { "type": 0 } }


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