Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8fd86ea9a7b948edbddecc2a086cef97b92c3477ed771281522bacd897b438f

Tx prefix hash: cb78f7642f9745e3b458476a6d0329ce4f0760696b5f03edc2ebb99ceb01a210
Tx public key: 7291047a062b4594c3854854f68703fdd7e0578f6b379dab296ca6be4523cfe2
Timestamp: 1771311302 Timestamp [UTC]: 2026-02-17 06:55:02 Age [y:d:h:m:s]: 00:275:22:52:21
Block: 1479591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202854 RingCT/type: yes/0
Extra: 017291047a062b4594c3854854f68703fdd7e0578f6b379dab296ca6be4523cfe2021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d60efcac9fbeea898ec1bfc0b6ef7b46d71d1e3890cd61a9f9a6fc804925717b 0.000600000000 1968943 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": 1479601, "vin": [ { "gen": { "height": 1479591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d60efcac9fbeea898ec1bfc0b6ef7b46d71d1e3890cd61a9f9a6fc804925717b" } } ], "extra": [ 1, 114, 145, 4, 122, 6, 43, 69, 148, 195, 133, 72, 84, 246, 135, 3, 253, 215, 224, 87, 143, 107, 55, 157, 171, 41, 108, 166, 190, 69, 35, 207, 226, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: