Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b4d3ef676f7bbaa806953797b7527f1e27ecf65ac688e0db288e0b60224f43f

Tx prefix hash: 4391621fada1af140a4c6ba75d926e512165be7c719485afbc990e866eaa8a9d
Tx public key: 0cac3af298efd811040d13fa8bf2540d07fed9d2067537f8f93b32928f5f4f9e
Timestamp: 1743989867 Timestamp [UTC]: 2025-04-07 01:37:47 Age [y:d:h:m:s]: 01:034:07:27:20
Block: 1255933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275596 RingCT/type: yes/0
Extra: 010cac3af298efd811040d13fa8bf2540d07fed9d2067537f8f93b32928f5f4f9e021100000001dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6904db625e757a90dba1f394a8e6cf569f62c9c0f52dd2f2564617074f0ad756 0.000600000000 1743040 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": 1255943, "vin": [ { "gen": { "height": 1255933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6904db625e757a90dba1f394a8e6cf569f62c9c0f52dd2f2564617074f0ad756" } } ], "extra": [ 1, 12, 172, 58, 242, 152, 239, 216, 17, 4, 13, 19, 250, 139, 242, 84, 13, 7, 254, 217, 210, 6, 117, 55, 248, 249, 59, 50, 146, 143, 95, 79, 158, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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: