Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf29b176bc8c1ff322eac9ce5d731b19390eb7d25c78687ee381189cfa0eedf

Tx prefix hash: e01ff69e1fb410f4e7c9d3d5b8fa1a478cf443ba5e4a8ebb5cce04793a89300f
Tx public key: 5b48f5bed8d464b4471412c42b284d9c1edaf3db62c1cbd7370bb6b74505b1c2
Timestamp: 1746951317 Timestamp [UTC]: 2025-05-11 08:15:17 Age [y:d:h:m:s]: 01:001:19:31:29
Block: 1280469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252098 RingCT/type: yes/0
Extra: 015b48f5bed8d464b4471412c42b284d9c1edaf3db62c1cbd7370bb6b74505b1c202110000000c9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c6f3f737b0d3673ab4d45f6375006cb96e08acecbd795d9927f94f8015fc88c 0.000600000000 1767856 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": 1280479, "vin": [ { "gen": { "height": 1280469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c6f3f737b0d3673ab4d45f6375006cb96e08acecbd795d9927f94f8015fc88c" } } ], "extra": [ 1, 91, 72, 245, 190, 216, 212, 100, 180, 71, 20, 18, 196, 43, 40, 77, 156, 30, 218, 243, 219, 98, 193, 203, 215, 55, 11, 182, 183, 69, 5, 177, 194, 2, 17, 0, 0, 0, 12, 159, 159, 230, 140, 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: