← previous blocknext block →recent activity
Analyzing
Block #106,950,307
23 transactions · 20 stateful · 2026-09-22 05:20:57 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,950,307 · 23 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
1w02w13w14w25w36w07w08w19w011w112w214w416w520w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8abaacb…b80d
0x34b655…2a6f
10 touches
10 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x385d548d…ad18
0x34b655…2a6f
6 touches
3 conflicts
0x8f130d96…e4eb
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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 0xf8abaacb72…2fb80d
Audit this contract →
← previous block·next block →recent activity