Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f792d99a8cc8e794ea73fdbc9455675a671b23902971f9e08df45695276c193d

Tx prefix hash: 8beebe5dc8ae8338f94811af81a119e346fbb636317b190941dfe983b779735d
Tx public key: f2064333d1a0abd6597d30addaa8ef73a1c7f52774f0a521be43020eccf42589
Timestamp: 1741943815 Timestamp [UTC]: 2025-03-14 09:16:55 Age [y:d:h:m:s]: 01:253:03:14:20
Block: 1239029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444465 RingCT/type: yes/0
Extra: 01f2064333d1a0abd6597d30addaa8ef73a1c7f52774f0a521be43020eccf42589021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd15086f3e7d9b6998e465c6fe81283b001dddf3b068e3bbff8c509a218c9614 0.000600000000 1725994 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": 1239039, "vin": [ { "gen": { "height": 1239029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd15086f3e7d9b6998e465c6fe81283b001dddf3b068e3bbff8c509a218c9614" } } ], "extra": [ 1, 242, 6, 67, 51, 209, 160, 171, 214, 89, 125, 48, 173, 218, 168, 239, 115, 161, 199, 245, 39, 116, 240, 165, 33, 190, 67, 2, 14, 204, 244, 37, 137, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: