Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60877948f996179d8257bd1756da2ef6b2c729a3a95970164eccd2ea9727b331

Tx prefix hash: 25baff299063f807daec768cafbf660b21c36d3e2c4e3fa36eb5c7828547e3b1
Tx public key: a32e13a223b347ae907d08df41daf515b25bc43477eb03f0d55e35eb61d321b6
Timestamp: 1716070030 Timestamp [UTC]: 2024-05-18 22:07:10 Age [y:d:h:m:s]: 02:184:01:13:35
Block: 1024972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656496 RingCT/type: yes/0
Extra: 01a32e13a223b347ae907d08df41daf515b25bc43477eb03f0d55e35eb61d321b602110000000152d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dbbcf33a17e821e118f0c0309b6b92f5ca615428a74b82502485e48a9183e4a7 0.000600000000 1491133 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": 1024982, "vin": [ { "gen": { "height": 1024972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbbcf33a17e821e118f0c0309b6b92f5ca615428a74b82502485e48a9183e4a7" } } ], "extra": [ 1, 163, 46, 19, 162, 35, 179, 71, 174, 144, 125, 8, 223, 65, 218, 245, 21, 178, 91, 196, 52, 119, 235, 3, 240, 213, 94, 53, 235, 97, 211, 33, 182, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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: