Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda6063d7e66c97f413f62c6425a63f20646e8e2dc5e73766775c4adf329dae3

Tx prefix hash: 5bcf1c79b8573a64ddbeee6e78cc9586588f09b6e4423b6b09788404d8d94bb7
Tx public key: 18157876b69875d4cfb801aae5c394f7d44a6b82b0c2c724220bd9631ee7afaa
Timestamp: 1742832718 Timestamp [UTC]: 2025-03-24 16:11:58 Age [y:d:h:m:s]: 01:243:04:24:48
Block: 1246361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437789 RingCT/type: yes/0
Extra: 0118157876b69875d4cfb801aae5c394f7d44a6b82b0c2c724220bd9631ee7afaa02110000000324ff4ea1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 13a0942d8a7c2d4d389ae3f2cd3160df5b981e6044058c9ba4d0a631c0952b69 0.000600000000 1733362 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": 1246371, "vin": [ { "gen": { "height": 1246361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a0942d8a7c2d4d389ae3f2cd3160df5b981e6044058c9ba4d0a631c0952b69" } } ], "extra": [ 1, 24, 21, 120, 118, 182, 152, 117, 212, 207, 184, 1, 170, 229, 195, 148, 247, 212, 74, 107, 130, 176, 194, 199, 36, 34, 11, 217, 99, 30, 231, 175, 170, 2, 17, 0, 0, 0, 3, 36, 255, 78, 161, 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: