Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1f50d3b56cdb21bfbbbec5d1edef30cb3afc3e26e72f05e436c8a7429ee5169

Tx prefix hash: ca4b40e671fbbbd17a21e087443f56463a380959a7220cbea003034698664417
Tx public key: 91d1d2c2bcec05defc0a1684b5ed17318ee5d5e6d04b4127edba4ac111799fa0
Timestamp: 1773722225 Timestamp [UTC]: 2026-03-17 04:37:05 Age [y:d:h:m:s]: 00:242:04:46:21
Block: 1499562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178485 RingCT/type: yes/0
Extra: 0191d1d2c2bcec05defc0a1684b5ed17318ee5d5e6d04b4127edba4ac111799fa0021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8cf7a0694d5e00bee2f64df037ccb62f263c6e7635852ea716b30d87b41b441 0.000600000000 1989224 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": 1499572, "vin": [ { "gen": { "height": 1499562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8cf7a0694d5e00bee2f64df037ccb62f263c6e7635852ea716b30d87b41b441" } } ], "extra": [ 1, 145, 209, 210, 194, 188, 236, 5, 222, 252, 10, 22, 132, 181, 237, 23, 49, 142, 229, 213, 230, 208, 75, 65, 39, 237, 186, 74, 193, 17, 121, 159, 160, 2, 17, 0, 0, 0, 3, 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: