← previous blocknext block →recent activity
Analyzing
Block #108,641,541
20 transactions · 19 stateful · 2026-09-28 03:16:06 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,641,541 · 20 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
1w02w15w06w27w38w49w510w611w713w116w517w618w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x526267fd…d9ee
0xd32edf…ff58
7 touches
6 conflicts
0xf311fcff…95eb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2de63fa2…1670
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity