← previous blocknext block →recent activity
Analyzing
Block #83,631,258
22 transactions · 20 stateful · 2026-06-25 15:54:45 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,258 · 22 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
6w07w18w29w310w417w019w020w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb3504d4…b05f
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x5be682e3…bb15
0x34b655…2a6f
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x5396d712…a139
0x34b655…2a6f
8 touches
6 conflicts
0x22468c32…cd6d
0x34b655…2a6f
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
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
10 conflicts on slot 0xbb3504d4cd…acb05f
Audit this contract →
← previous block·next block →recent activity