← previous blocknext block →recent activity
Analyzing
Block #106,932,056
16 transactions · 16 stateful · 2026-09-22 03:49:05 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,932,056 · 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
2w05w17w28w311w012w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93e45251…6e19
0x34b655…2a6f
10 touches
10 conflicts
0xc74116ee…6ec0
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0x93e45251f3…c56e19
Audit this contract →
← previous block·next block →recent activity