Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a558317a3fc26cfa8c1111457ef5fb7732b7753d916d43be34d52191dfabff

Tx prefix hash: b3ee0f89f814abe8cba667e2b7780fd7e481971e9c73eeb06c5ee135c411d574
Tx public key: f2dcfd98ef5d431f29cdafe9ba5975599e1fd7c3e13a9c6d315f6e714027ebf6
Timestamp: 1747388361 Timestamp [UTC]: 2025-05-16 09:39:21 Age [y:d:h:m:s]: 01:069:07:25:12
Block: 1284078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299036 RingCT/type: yes/0
Extra: 01f2dcfd98ef5d431f29cdafe9ba5975599e1fd7c3e13a9c6d315f6e714027ebf60211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa2ff0d7750ef6be1f28e85977c9ce3a84f0b4b2b59ca8723147f445f8d51b79 0.000600000000 1771513 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": 1284088, "vin": [ { "gen": { "height": 1284078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa2ff0d7750ef6be1f28e85977c9ce3a84f0b4b2b59ca8723147f445f8d51b79" } } ], "extra": [ 1, 242, 220, 253, 152, 239, 93, 67, 31, 41, 205, 175, 233, 186, 89, 117, 89, 158, 31, 215, 195, 225, 58, 156, 109, 49, 95, 110, 113, 64, 39, 235, 246, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: