Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6588ac73db651e33a5ed150d89e594091e449d7d68399f8704f540c8a3e729ca

Tx prefix hash: 3d5a2ebe037ea2f6fee59abebd50b4ca7408d62c11217b42da55ebf01343f996
Tx public key: 0ce87cca1d7a5dc129f0b6a1cd0c0c7e9539872635e3e2afe4cacee477d2dde3
Timestamp: 1745885290 Timestamp [UTC]: 2025-04-29 00:08:10 Age [y:d:h:m:s]: 01:204:07:12:13
Block: 1271654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410064 RingCT/type: yes/0
Extra: 010ce87cca1d7a5dc129f0b6a1cd0c0c7e9539872635e3e2afe4cacee477d2dde30211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: eb886e3c0b36bbb9623618709f43d83d8d330ef88f8f6ad09994d0a2acaf7320 0.000600000000 1758921 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": 1271664, "vin": [ { "gen": { "height": 1271654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb886e3c0b36bbb9623618709f43d83d8d330ef88f8f6ad09994d0a2acaf7320" } } ], "extra": [ 1, 12, 232, 124, 202, 29, 122, 93, 193, 41, 240, 182, 161, 205, 12, 12, 126, 149, 57, 135, 38, 53, 227, 226, 175, 228, 202, 206, 228, 119, 210, 221, 227, 2, 17, 0, 0, 0, 4, 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: