← previous blocknext block →recent activity
Analyzing
Block #106,932,414
17 transactions · 17 stateful · 2026-09-22 03:50:53 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,414 · 17 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
1w03w04w15w26w37w18w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9375a764…dca1
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xb7aa9720…56df
0x34b655…2a6f
8 touches
6 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
8 touches
6 conflicts
0x503df629…59cb
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x3e163287…f328
0x34b655…2a6f
4 touches
1 conflict
0x858e40c0…7e30
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 0x9375a764b5…f0dca1
Audit this contract →
← previous block·next block →recent activity