Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc377ef67f7d5eb9faa2253f4f20efb24c988be614895ad3bcc3b2b41a26186

Tx prefix hash: f419ec8491f518147eb08bd5020630795086ce79f80fbb5e2a7e1e217f80832d
Tx public key: 64a810bbaab930dd32d9e39f97d11ba056f88c9444ae3f8c261dc4d3dfd4f46e
Timestamp: 1747007786 Timestamp [UTC]: 2025-05-11 23:56:26 Age [y:d:h:m:s]: 01:192:14:08:57
Block: 1280927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401812 RingCT/type: yes/0
Extra: 0164a810bbaab930dd32d9e39f97d11ba056f88c9444ae3f8c261dc4d3dfd4f46e0211000000051f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c8026aa43786bf09f24202ae233e1a240d17bd5ce2a6f6d9c3f372d0a161ccb8 0.000600000000 1768320 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": 1280937, "vin": [ { "gen": { "height": 1280927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8026aa43786bf09f24202ae233e1a240d17bd5ce2a6f6d9c3f372d0a161ccb8" } } ], "extra": [ 1, 100, 168, 16, 187, 170, 185, 48, 221, 50, 217, 227, 159, 151, 209, 27, 160, 86, 248, 140, 148, 68, 174, 63, 140, 38, 29, 196, 211, 223, 212, 244, 110, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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: