← previous blocknext block →recent activity
Analyzing
Block #107,814,736
22 transactions · 19 stateful · 2026-09-25 05:54:23 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,814,736 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w010w111w012w113w214w218w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa23b9051…392f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5b952815…d233
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9287
0x34ae4d…3fc5
2 touches
0 conflicts
0x3ba7edbb…80e6
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity