← previous blocknext block →recent activity
Analyzing
Block #83,642,754
16 transactions · 15 stateful · 2026-06-25 17:11:33 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,642,754 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w08w19w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe334a6b5…173c
0x34b655…2a6f
8 touches
6 conflicts
0xfd4e2262…cd8c
0x34b655…2a6f
8 touches
6 conflicts
0x524e7313…5438
0x34b655…2a6f
6 touches
3 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0x3ec82b22…1f46
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe99d8e68…a16e
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 0xe334a6b501…be173c
Audit this contract →
← previous block·next block →recent activity