← previous blocknext block →recent activity
Analyzing
Block #83,632,918
29 transactions · 26 stateful · 2026-06-25 16:05:51 UTC
Parallelism
59/100
Blocked
54%
Avg conflicts / tx
2.31
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #83,632,918 · 29 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w518w421w723w924w1026w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xcde75077…ccee
0x34b655…2a6f
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x5396d712…a139
0x34b655…2a6f
12 touches
15 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
12 touches
15 conflicts
0x403d1735…de44
0x34b655…2a6f
11 touches
16 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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity