Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d96fd12cdc926c01ce8fd80da3b2784d1fd855931ec984a26f22f15381c64be

Tx prefix hash: f8bae69a2c39a1990dfefac141fc71790f047f0494c4bce22a2e4df6711e6c92
Tx public key: 2dd0c61c4b6f575d6e8e90560f0b276f389d3097f8a0f7446f3c61153bced609
Timestamp: 1758319928 Timestamp [UTC]: 2025-09-19 22:12:08 Age [y:d:h:m:s]: 01:063:12:52:07
Block: 1372131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311363 RingCT/type: yes/0
Extra: 012dd0c61c4b6f575d6e8e90560f0b276f389d3097f8a0f7446f3c61153bced609021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 12953236e930d3322a83001aa85e1902e03dd64b6b1bf0dfcb5cfd37f1f76344 0.000600000000 1860216 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": 1372141, "vin": [ { "gen": { "height": 1372131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12953236e930d3322a83001aa85e1902e03dd64b6b1bf0dfcb5cfd37f1f76344" } } ], "extra": [ 1, 45, 208, 198, 28, 75, 111, 87, 93, 110, 142, 144, 86, 15, 11, 39, 111, 56, 157, 48, 151, 248, 160, 247, 68, 111, 60, 97, 21, 59, 206, 214, 9, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: