← previous blocknext block →recent activity
Analyzing
Block #83,670,851
14 transactions · 11 stateful · 2026-06-25 20:18:57 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,670,851 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4702f73…926c
0x34b655…2a6f
6 touches
3 conflicts
0x1274880c…3cdc
0x34b655…2a6f
6 touches
3 conflicts
0x13c5b486…d41e
0x34b655…2a6f
6 touches
3 conflicts
0xf4cdb4e5…78d7
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0xb2271c91…685a
0x34b655…2a6f
4 touches
1 conflict
0x65df2980…8edc
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
3 conflicts on slot 0xd4702f73d1…46926c
Audit this contract →
← previous block·next block →recent activity