← previous blocknext block →recent activity
Analyzing
Block #83,628,456
20 transactions · 18 stateful · 2026-06-25 15:36:03 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,628,456 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w513w614w719w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e86dd1e…dc3e
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
12 touches
15 conflicts
0x55c19be0…00a2
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x9d62d2dd…657e
0x34b655…2a6f
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 conflicts
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
28 conflicts on slot 0x2e86dd1e84…99dc3e
Audit this contract →
← previous block·next block →recent activity