Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e2f710c033b5c9325be8508bc60779633492000e1547e38cd9a8f7c508cbb6

Tx prefix hash: 0f75c5fd5b4f1632e5d98921f2e2745f8df5339ca95dfb0d4e3132d066c6e4a8
Tx public key: 35dc08ec1dce247c044da36a5eb322df9b8c4bea91297d1f8b0c3b5c6ab050f7
Timestamp: 1733815375 Timestamp [UTC]: 2024-12-10 07:22:55 Age [y:d:h:m:s]: 01:345:03:29:08
Block: 1171993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510636 RingCT/type: yes/0
Extra: 0135dc08ec1dce247c044da36a5eb322df9b8c4bea91297d1f8b0c3b5c6ab050f7021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0251eb38b9ed94fcd4e0c6f0d2801a347a7347507f82af01ba5a3409978986e0 0.000600000000 1657826 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": 1172003, "vin": [ { "gen": { "height": 1171993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0251eb38b9ed94fcd4e0c6f0d2801a347a7347507f82af01ba5a3409978986e0" } } ], "extra": [ 1, 53, 220, 8, 236, 29, 206, 36, 124, 4, 77, 163, 106, 94, 179, 34, 223, 155, 140, 75, 234, 145, 41, 125, 31, 139, 12, 59, 92, 106, 176, 80, 247, 2, 17, 0, 0, 0, 2, 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: