Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4871da82d67ca3f5b71156ff7775eed81afd27bdf5869b097fa94f968036cd78

Tx prefix hash: a8b53ef9255ef8dc75db42a1a803f8724f657b01e09c5d81bf8fa716a16b9c92
Tx public key: f2088825a6724fe4b2a0bbde48773abaa44f418ec9b8bdd5f45986a7d08275fa
Timestamp: 1740852425 Timestamp [UTC]: 2025-03-01 18:07:05 Age [y:d:h:m:s]: 01:263:17:06:17
Block: 1229969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452678 RingCT/type: yes/0
Extra: 01f2088825a6724fe4b2a0bbde48773abaa44f418ec9b8bdd5f45986a7d08275fa021100000008007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06e9f71986399620dd00db4c21e988dbbf35ee2e5efbc6ea68087aaa7d01adf8 0.000600000000 1716860 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": 1229979, "vin": [ { "gen": { "height": 1229969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06e9f71986399620dd00db4c21e988dbbf35ee2e5efbc6ea68087aaa7d01adf8" } } ], "extra": [ 1, 242, 8, 136, 37, 166, 114, 79, 228, 178, 160, 187, 222, 72, 119, 58, 186, 164, 79, 65, 142, 201, 184, 189, 213, 244, 89, 134, 167, 208, 130, 117, 250, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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: