Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2559ca0e30dbd7f6553439d3de4ea95652cdd161e58b85f4eda940263bb43d0

Tx prefix hash: 1b2deae8c1536d1830c191cbf1ce759ffdfbf13565a59e20993cd6640e0acc7b
Tx public key: b7e4b496e70f1bc2acb80c9e95ffd343e48be2efa4f131176a961cfc16ec3d1d
Timestamp: 1761876536 Timestamp [UTC]: 2025-10-31 02:08:56 Age [y:d:h:m:s]: 01:022:06:59:26
Block: 1401623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281871 RingCT/type: yes/0
Extra: 01b7e4b496e70f1bc2acb80c9e95ffd343e48be2efa4f131176a961cfc16ec3d1d0211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7bf7005dfb9ee562ebb3bdc0744635acb1f7b69d1a2ff4f61694b7bb6f6a3689 0.000600000000 1889942 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": 1401633, "vin": [ { "gen": { "height": 1401623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf7005dfb9ee562ebb3bdc0744635acb1f7b69d1a2ff4f61694b7bb6f6a3689" } } ], "extra": [ 1, 183, 228, 180, 150, 231, 15, 27, 194, 172, 184, 12, 158, 149, 255, 211, 67, 228, 139, 226, 239, 164, 241, 49, 23, 106, 150, 28, 252, 22, 236, 61, 29, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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: