← previous blocknext block →recent activity
Analyzing
Block #83,626,962
47 transactions · 35 stateful · 2026-06-25 15:26:02 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
2.3
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,626,962 · 47 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w210w311w412w513w015w119w020w121w222w323w424w525w626w727w828w929w1042w944w1145w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x0afbcc81…fba0
0x34b655…2a6f
10 touches
10 conflicts
0x3b8acfe4…a3d9
0x34b655…2a6f
10 touches
10 conflicts
0x5d2b5661…df66
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity