← previous blocknext block →recent activity
Analyzing
Block #106,916,125
26 transactions · 24 stateful · 2026-09-22 02:28:54 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,916,125 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w09w110w213w314w415w516w617w720w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518221db…65f7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x05ac61b0…7daa
0x34b655…2a6f
8 touches
6 conflicts
0x04615695…46ec
0x34b655…2a6f
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
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
10 conflicts on slot 0x518221db7f…5465f7
Audit this contract →
← previous block·next block →recent activity