← previous blocknext block →recent activity
Analyzing
Block #83,633,065
12 transactions · 10 stateful · 2026-06-25 16:06:50 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,633,065 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d4b0baf…1423
0x34b655…2a6f
8 touches
6 conflicts
0x619f5683…5bd4
0x34b655…2a6f
5 touches
3 conflicts
0xe55f19fd…5aaa
0x34b655…2a6f
4 touches
1 conflict
0xcff90c3c…0456
0x34b655…2a6f
4 touches
1 conflict
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0xd58b9a66…1c23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x1d4b0bafd5…641423
Audit this contract →
← previous block·next block →recent activity