← previous blocknext block →recent activity
Analyzing
Block #106,916,111
17 transactions · 17 stateful · 2026-09-22 02:28:50 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.94
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,916,111 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w28w39w410w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
16 touches
28 conflicts
0xe3425a1e…da15
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x34eb3605…9253
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x4870c9a7…ef7c
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
28 conflicts on slot 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity