Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c8acdd16630c0fc1c02a506eaa6de28ef5b0c7815cb2b7950c605b31cd4169e

Tx prefix hash: 9ecb920e8128fc99a3b0d1020755b0474a4fef1fb2dd44073dbdef46848c5df9
Tx public key: 0785bd42e2272c581ac1581f8103ff06d975313aefa6489ccf04ebab0f53249f
Timestamp: 1754445612 Timestamp [UTC]: 2025-08-06 02:00:12 Age [y:d:h:m:s]: 01:108:05:43:05
Block: 1341174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342320 RingCT/type: yes/0
Extra: 010785bd42e2272c581ac1581f8103ff06d975313aefa6489ccf04ebab0f53249f02110000000bad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 21aaa53f84849080f2a99d8373af344b16f91319c025231339f440f14df87a2d 0.000600000000 1828997 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": 1341184, "vin": [ { "gen": { "height": 1341174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21aaa53f84849080f2a99d8373af344b16f91319c025231339f440f14df87a2d" } } ], "extra": [ 1, 7, 133, 189, 66, 226, 39, 44, 88, 26, 193, 88, 31, 129, 3, 255, 6, 217, 117, 49, 58, 239, 166, 72, 156, 207, 4, 235, 171, 15, 83, 36, 159, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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: