Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18d9e278a41ce1ae5af2fb2ce5c5f4d2a6fe2f0f1a12d5affaf1d57c092c425

Tx prefix hash: 8fd97c3096c1bbceee6c4cf109130214cf7dd14c389e58d36033ab6f8c29f364
Tx public key: d857d06541f86ddc3cfda3b292d6064ebf88c8cebee3d0c3e62477bc6a5df713
Timestamp: 1747819434 Timestamp [UTC]: 2025-05-21 09:23:54 Age [y:d:h:m:s]: 01:185:10:49:04
Block: 1287663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396487 RingCT/type: yes/0
Extra: 01d857d06541f86ddc3cfda3b292d6064ebf88c8cebee3d0c3e62477bc6a5df7130211000000071f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0042886552c93235128b68b508c53c75406deb6af6a26f0093984836a2d0718 0.000600000000 1775130 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": 1287673, "vin": [ { "gen": { "height": 1287663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0042886552c93235128b68b508c53c75406deb6af6a26f0093984836a2d0718" } } ], "extra": [ 1, 216, 87, 208, 101, 65, 248, 109, 220, 60, 253, 163, 178, 146, 214, 6, 78, 191, 136, 200, 206, 190, 227, 208, 195, 230, 36, 119, 188, 106, 93, 247, 19, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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: