Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82a21ec135ffe75e625e8d232133decfa204cd5354f4cf6b4012d7e279e8a04d

Tx prefix hash: d8462f0d87665cba19609bab3c7523d54d03a5a0c89e724a60a68419b1d43c70
Tx public key: 0dc67bf3c6abfee1d0b3c1c0654814d9e5db1555cbfc96a9f7a7a3a071fa7259
Timestamp: 1760831471 Timestamp [UTC]: 2025-10-18 23:51:11 Age [y:d:h:m:s]: 01:033:01:17:46
Block: 1392966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290097 RingCT/type: yes/0
Extra: 010dc67bf3c6abfee1d0b3c1c0654814d9e5db1555cbfc96a9f7a7a3a071fa72590211000000082609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 15d08d8d79831b0aa1f69e8deda21c38ca172df9f70d51cdc634459a45aa4c8d 0.000600000000 1881223 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": 1392976, "vin": [ { "gen": { "height": 1392966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15d08d8d79831b0aa1f69e8deda21c38ca172df9f70d51cdc634459a45aa4c8d" } } ], "extra": [ 1, 13, 198, 123, 243, 198, 171, 254, 225, 208, 179, 193, 192, 101, 72, 20, 217, 229, 219, 21, 85, 203, 252, 150, 169, 247, 167, 163, 160, 113, 250, 114, 89, 2, 17, 0, 0, 0, 8, 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: