Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86247a7c48ff55ac221c3fc13158e2baec14c9fbb359dce5323b6e00dfa5be8a

Tx prefix hash: 86ac8e1bf8858dd2a7097cd170b06a98681f1a5d0b61f91ae11d0f9368cd1f5d
Tx public key: afa969d0ac3107d0bd79e58e2fba0a61dd88f592bb9c1302fbcdd5ad50e5c8b8
Timestamp: 1756968032 Timestamp [UTC]: 2025-09-04 06:40:32 Age [y:d:h:m:s]: 01:072:01:10:58
Block: 1360999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317749 RingCT/type: yes/0
Extra: 01afa969d0ac3107d0bd79e58e2fba0a61dd88f592bb9c1302fbcdd5ad50e5c8b8021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6ecf8da19feb5349b67d5c72605aea0cf4900099684ddb7f5fac958af8e65f1 0.000600000000 1849012 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": 1361009, "vin": [ { "gen": { "height": 1360999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ecf8da19feb5349b67d5c72605aea0cf4900099684ddb7f5fac958af8e65f1" } } ], "extra": [ 1, 175, 169, 105, 208, 172, 49, 7, 208, 189, 121, 229, 142, 47, 186, 10, 97, 221, 136, 245, 146, 187, 156, 19, 2, 251, 205, 213, 173, 80, 229, 200, 184, 2, 17, 0, 0, 0, 1, 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: