← previous blocknext block →recent activity
Analyzing
Block #108,961,104
23 transactions · 17 stateful · 2026-09-29 06:08:48 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,961,104 · 23 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
1w06w07w19w110w211w312w416w118w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19131f55…a985
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x50a294ea…9b01
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 0x19131f5525…66a985
Audit this contract →
← previous block·next block →recent activity