Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0720fd22f2d79b2b7f0de8b1dc9e32eb1f14db28f8138cc5447f02a5a60dcfa8

Tx prefix hash: 78f9d30a9a4a87502f0b8e88a1dbeac7c96a6e9721eff4d714d35285ea8c33b4
Tx public key: 7697ea36dc4012ce033efe0b1c5b3f8c638ecd1a5f5b4913aeb847ad06e1bdca
Timestamp: 1785552052 Timestamp [UTC]: 2026-08-01 02:40:52 Age [y:d:h:m:s]: 00:113:04:45:20
Block: 1603246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 80248 RingCT/type: yes/0
Extra: 017697ea36dc4012ce033efe0b1c5b3f8c638ecd1a5f5b4913aeb847ad06e1bdca

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3869e53949d9d7adce28a21d6681ba14f221ae1a097b0b97912642ff5df44ad0 0.000600000000 2093264 of 15 <46>

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": 1603256, "vin": [ { "gen": { "height": 1603246 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3869e53949d9d7adce28a21d6681ba14f221ae1a097b0b97912642ff5df44ad0", "view_tag": "46" } } } ], "extra": [ 1, 118, 151, 234, 54, 220, 64, 18, 206, 3, 62, 254, 11, 28, 91, 63, 140, 99, 142, 205, 26, 95, 91, 73, 19, 174, 184, 71, 173, 6, 225, 189, 202 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: