Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b68df41473433aa424659853cb10da9ddf015155b11d01aae37ea11ff9bb26

Tx prefix hash: 697dcddf7205528f6eb9a964272b21c072307bf0af41e60567c0eb03c09939ab
Tx public key: 46b60088d9749943c6d84a072681def9a55ddbfc998de858c01b8cca00233f49
Timestamp: 1772972421 Timestamp [UTC]: 2026-03-08 12:20:21 Age [y:d:h:m:s]: 00:251:11:19:37
Block: 1493358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185131 RingCT/type: yes/0
Extra: 0146b60088d9749943c6d84a072681def9a55ddbfc998de858c01b8cca00233f49021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 941c6a8a1eab383b06b615ff48d1cb013a5daf62b94dce28c42111ce4d518d58 0.000600000000 1982914 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": 1493368, "vin": [ { "gen": { "height": 1493358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941c6a8a1eab383b06b615ff48d1cb013a5daf62b94dce28c42111ce4d518d58" } } ], "extra": [ 1, 70, 182, 0, 136, 217, 116, 153, 67, 198, 216, 74, 7, 38, 129, 222, 249, 165, 93, 219, 252, 153, 141, 232, 88, 192, 27, 140, 202, 0, 35, 63, 73, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: