← previous blocknext block →recent activity
Analyzing
Block #106,959,005
16 transactions · 16 stateful · 2026-09-22 06:04:44 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,959,005 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w08w19w110w211w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d81790c…b9f7
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x7be75412…fd59
0x34b655…2a6f
6 touches
3 conflicts
0xa4a1ecf7…9e63
0x34b655…2a6f
6 touches
3 conflicts
0xc35d158c…6271
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x5cad7217…bdbf
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1d81790c4e…7cb9f7
Audit this contract →
← previous block·next block →recent activity