← previous blocknext block →recent activity
Analyzing
Block #83,485,234
14 transactions · 11 stateful · 2026-06-24 23:40:28 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,485,234 · 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
5w06w17w28w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x864353d4…dcb7
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x4e300a14…0bc3
0x34b655…2a6f
4 touches
1 conflict
0xab24a15c…55b0
0x34b655…2a6f
4 touches
1 conflict
0x1ef9fddf…b6a7
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 0x864353d495…99dcb7
Audit this contract →
← previous block·next block →recent activity