← previous blocknext block →recent activity
Analyzing
Block #106,931,582
25 transactions · 25 stateful · 2026-09-22 03:46:42 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.28
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,931,582 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w312w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469dac8d…3411
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x66511956…e9dc
0x34b655…2a6f
12 touches
15 conflicts
0x155e52ca…fac7
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x3740f434…cccb
0x34b655…2a6f
8 touches
6 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xa088bd64…9bad
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
21 conflicts on slot 0x469dac8dcd…223411
Audit this contract →
← previous block·next block →recent activity