Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82e0bb8b79dcf11b250ceb1b6ce0006bf1c04bfa3e4758c16752403f2ccf298a

Tx prefix hash: 5888204d4760e77ad3c6bed7f202188072bcce7ba33a93c4536292ac4028625f
Tx public key: 7eb86c85072bb73fc6bd8c7c38dca7e645b7fa5d6b9eca9acc05e407a3faed3d
Timestamp: 1754593316 Timestamp [UTC]: 2025-08-07 19:01:56 Age [y:d:h:m:s]: 00:301:06:54:55
Block: 1342300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209230 RingCT/type: yes/0
Extra: 017eb86c85072bb73fc6bd8c7c38dca7e645b7fa5d6b9eca9acc05e407a3faed3d0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bcc34862e07bdd1ea126b46b1acdde484b032923733f4d54d58952cfdfba41cf 0.000600000000 1830131 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": 1342310, "vin": [ { "gen": { "height": 1342300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcc34862e07bdd1ea126b46b1acdde484b032923733f4d54d58952cfdfba41cf" } } ], "extra": [ 1, 126, 184, 108, 133, 7, 43, 183, 63, 198, 189, 140, 124, 56, 220, 167, 230, 69, 183, 250, 93, 107, 158, 202, 154, 204, 5, 228, 7, 163, 250, 237, 61, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: