Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da16c0a289eed8602874e0f10ae5e37dde72017221959d1fb55d095978c19fa1

Tx prefix hash: 9bde8f6809330840503ee6ec0d426c192e25f340c27122ecef240e5957b54fd3
Tx public key: 349d0664de8ff15a1f8d716af5de702dc8d98c3592731cd0576dea952388c237
Timestamp: 1744018202 Timestamp [UTC]: 2025-04-07 09:30:02 Age [y:d:h:m:s]: 01:220:03:55:32
Block: 1256175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421249 RingCT/type: yes/0
Extra: 01349d0664de8ff15a1f8d716af5de702dc8d98c3592731cd0576dea952388c2370211000000116c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f993ed7bfb449d5cd6127578e067b4a1fcc3acd47b7849c2b82a8424347d6d1 0.000600000000 1743288 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": 1256185, "vin": [ { "gen": { "height": 1256175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f993ed7bfb449d5cd6127578e067b4a1fcc3acd47b7849c2b82a8424347d6d1" } } ], "extra": [ 1, 52, 157, 6, 100, 222, 143, 241, 90, 31, 141, 113, 106, 245, 222, 112, 45, 200, 217, 140, 53, 146, 115, 28, 208, 87, 109, 234, 149, 35, 136, 194, 55, 2, 17, 0, 0, 0, 17, 108, 152, 170, 61, 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: