Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b888eb4c4e8689a049703c18e8fa6d4ec05b4ba710c417d3875a32ac1f25653c

Tx prefix hash: 0d92947123b3ad013a651c0f1a27424ed6666110a4852be40e4f3216274513da
Tx public key: 22dfee5f3ea0e643ff2c3f27fc4cc30231fbd435d74dac8ddebe4cc0e6cb955e
Timestamp: 1674326291 Timestamp [UTC]: 2023-01-21 18:38:11 Age [y:d:h:m:s]: 03:302:16:17:58
Block: 679766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1002067 RingCT/type: yes/0
Extra: 0122dfee5f3ea0e643ff2c3f27fc4cc30231fbd435d74dac8ddebe4cc0e6cb955e021100000001272bcc39000000000000000000

1 output(s) for total of 0.003432835563 xmr

stealth address amount amount idx tag
00: 5aff37a2bbf6fda4e10413dfc105eb1ff52c56d2fcb9de448267f2467b33c1c9 0.003432835563 1121777 of 0 -

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": 679776, "vin": [ { "gen": { "height": 679766 } } ], "vout": [ { "amount": 3432835563, "target": { "key": "5aff37a2bbf6fda4e10413dfc105eb1ff52c56d2fcb9de448267f2467b33c1c9" } } ], "extra": [ 1, 34, 223, 238, 95, 62, 160, 230, 67, 255, 44, 63, 39, 252, 76, 195, 2, 49, 251, 212, 53, 215, 77, 172, 141, 222, 190, 76, 192, 230, 203, 149, 94, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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: