Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686a0fed3c2c2eb061cda88e42c1d1379f8fe169c1859439e2121f0a4dffb0af

Tx prefix hash: 33deee47c7ece11c17677d5d58fdcbf7910b71d2f6c109718065b56d4b3cce8e
Tx public key: 8f89ee38241407f51b2b5535d9ed764e4143b3ac077c4161ea8be8c17b887891
Timestamp: 1754493531 Timestamp [UTC]: 2025-08-06 15:18:51 Age [y:d:h:m:s]: 01:105:23:30:06
Block: 1341546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341216 RingCT/type: yes/0
Extra: 018f89ee38241407f51b2b5535d9ed764e4143b3ac077c4161ea8be8c17b887891021100000003e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a286a1c8d63550dba8b87e538d88f457effc76187cf0df195b4df9a6f5a713e 0.000600000000 1829371 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": 1341556, "vin": [ { "gen": { "height": 1341546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a286a1c8d63550dba8b87e538d88f457effc76187cf0df195b4df9a6f5a713e" } } ], "extra": [ 1, 143, 137, 238, 56, 36, 20, 7, 245, 27, 43, 85, 53, 217, 237, 118, 78, 65, 67, 179, 172, 7, 124, 65, 97, 234, 139, 232, 193, 123, 136, 120, 145, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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: