Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c97aad084492f40d07d7f48199fdb1d0a206930c1bc90ebe820141f50cb2dc6

Tx prefix hash: 8f23c05c2ead49f3d7362675e5aad67ba9443087932cc7f9b9a0cef15ebed136
Tx public key: 6b9ff8dd20a955796aba60300e5dd96071dda955955c0b18d8fd921de66c4ba8
Timestamp: 1742494915 Timestamp [UTC]: 2025-03-20 18:21:55 Age [y:d:h:m:s]: 01:244:04:30:31
Block: 1243592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438629 RingCT/type: yes/0
Extra: 016b9ff8dd20a955796aba60300e5dd96071dda955955c0b18d8fd921de66c4ba8021100000001bfa77623000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 303dc1ce23c426b68b30e4dc706f49218d9440d58a9b69eb155f4a38b40db13a 0.000600000000 1730577 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": 1243602, "vin": [ { "gen": { "height": 1243592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "303dc1ce23c426b68b30e4dc706f49218d9440d58a9b69eb155f4a38b40db13a" } } ], "extra": [ 1, 107, 159, 248, 221, 32, 169, 85, 121, 106, 186, 96, 48, 14, 93, 217, 96, 113, 221, 169, 85, 149, 92, 11, 24, 216, 253, 146, 29, 230, 108, 75, 168, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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: