Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c91d70a5324765675438d8d991f5acd5607e8e9d2a4361d907b6cb71b9a5a9f

Tx prefix hash: 682e880857eb91e90c7aaebd539091211827da20414e538a669b0df31249ea8a
Tx public key: 72d0b9822b4410e925e00b291aecce3e8bedddd9e950b11e88c9d2564e5f7e03
Timestamp: 1755135237 Timestamp [UTC]: 2025-08-14 01:33:57 Age [y:d:h:m:s]: 00:274:03:52:14
Block: 1346393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187751 RingCT/type: yes/0
Extra: 0172d0b9822b4410e925e00b291aecce3e8bedddd9e950b11e88c9d2564e5f7e030211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e4a4c72cfa0643141e5ec787fe7e2dd0f4063a3b78ef4121d16392a5187317f 0.000600000000 1834292 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": 1346403, "vin": [ { "gen": { "height": 1346393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4a4c72cfa0643141e5ec787fe7e2dd0f4063a3b78ef4121d16392a5187317f" } } ], "extra": [ 1, 114, 208, 185, 130, 43, 68, 16, 233, 37, 224, 11, 41, 26, 236, 206, 62, 139, 237, 221, 217, 233, 80, 177, 30, 136, 201, 210, 86, 78, 95, 126, 3, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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: