← previous blocknext block →recent activity
Analyzing
Block #83,575,678
10 transactions · 10 stateful · 2026-06-25 09:43:37 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,575,678 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fbe9f83…de6e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8e3b3446…91ce
0x065c9d…c394
3 touches
1 conflict
0x07d38204…c7f7
0x065c9d…c394
3 touches
1 conflict
0x392c8559…deec
0x065c9d…c394
2 touches
0 conflicts
0x7e9c7091…a402
0x065c9d…c394
2 touches
0 conflicts
0xa0613a67…945d
0x065c9d…c394
2 touches
0 conflicts
0xa187006c…f740
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x7fbe9f8358…bcde6e
Audit this contract →
← previous block·next block →recent activity