← previous blocknext block →recent activity
Analyzing
Block #83,639,743
18 transactions · 16 stateful · 2026-06-25 16:51:27 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,639,743 · 18 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
1w02w14w05w16w28w311w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee7978e9…2869
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
6 touches
3 conflicts
0x28e6fd87…97f7
0x34b655…2a6f
4 touches
1 conflict
0x2c4dca93…b0a9
0x34b655…2a6f
4 touches
1 conflict
0x4629ed22…962d
0x34b655…2a6f
4 touches
1 conflict
0x6a895222…82d6
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
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 0xee7978e97a…ed2869
Audit this contract →
← previous block·next block →recent activity