Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3262a5b33c106b7c7ca027db656cde2b6093986d870fb5a0b223e297455482e

Tx prefix hash: bfd6121b61fa97d21ed1ecc845e94260fbdea21b615909a1a77143b667a02e59
Tx public key: 140ac63ddb27305b9ba21662dac189fde100b3adf6225cbe93cec4806e1c7e29
Timestamp: 1743163537 Timestamp [UTC]: 2025-03-28 12:05:37 Age [y:d:h:m:s]: 01:150:10:10:37
Block: 1249104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371872 RingCT/type: yes/0
Extra: 01140ac63ddb27305b9ba21662dac189fde100b3adf6225cbe93cec4806e1c7e2902110000000b9ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9ad5a9b3a2e44306131553feabf509d7db04bdb2ef9b9e064028168ef5e6b7e4 0.000600000000 1736139 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": 1249114, "vin": [ { "gen": { "height": 1249104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ad5a9b3a2e44306131553feabf509d7db04bdb2ef9b9e064028168ef5e6b7e4" } } ], "extra": [ 1, 20, 10, 198, 61, 219, 39, 48, 91, 155, 162, 22, 98, 218, 193, 137, 253, 225, 0, 179, 173, 246, 34, 92, 190, 147, 206, 196, 128, 110, 28, 126, 41, 2, 17, 0, 0, 0, 11, 155, 166, 41, 223, 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: