← previous blocknext block →recent activity
Analyzing
Block #106,915,845
21 transactions · 20 stateful · 2026-09-22 02:27:29 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,915,845 · 21 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
1w02w14w05w16w27w38w49w011w012w113w114w216w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9c8c872…e38c
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x18d21f98…ec62
0x6f6493…b480
4 touches
1 conflict
0x18d21f98…ec66
0x6f6493…b480
4 touches
1 conflict
0x18e08946…dda0
0x6f6493…b480
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 0xe9c8c87257…02e38c
Audit this contract →
← previous block·next block →recent activity