Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a93d0926427101df22183e13eb29c20cc70270cd712b1ec64664832be0620713

Tx prefix hash: b216e3bc88d1845d5a2d5097110cf15a5ed3eb80ac029853bdd25da3ca8433d6
Tx public key: 68a7ed211da598ad12b0a66f8b1a76aceba25f30a3f1d5a2369ae969e35d3028
Timestamp: 1690435373 Timestamp [UTC]: 2023-07-27 05:22:53 Age [y:d:h:m:s]: 03:118:22:12:17
Block: 812724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 870770 RingCT/type: yes/0
Extra: 0168a7ed211da598ad12b0a66f8b1a76aceba25f30a3f1d5a2369ae969e35d3028021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.001244824483 xmr

stealth address amount amount idx tag
00: 9c3e63c58f4fd1df2b2b3c379d4da03775aeaad191883571a65f4c8e0ee95a07 0.001244824483 1264431 of 0 -

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": 812734, "vin": [ { "gen": { "height": 812724 } } ], "vout": [ { "amount": 1244824483, "target": { "key": "9c3e63c58f4fd1df2b2b3c379d4da03775aeaad191883571a65f4c8e0ee95a07" } } ], "extra": [ 1, 104, 167, 237, 33, 29, 165, 152, 173, 18, 176, 166, 111, 139, 26, 118, 172, 235, 162, 95, 48, 163, 241, 213, 162, 54, 154, 233, 105, 227, 93, 48, 40, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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: