← previous blocknext block →recent activity
Analyzing
Block #108,499,479
23 transactions · 19 stateful · 2026-09-27 15:20:40 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,499,479 · 23 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
3w07w19w110w211w215w017w018w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0998a89…1f5a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda9a4d3d…9c4b
0xd32edf…ff58
5 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0xa0998a8998…e71f5a
Audit this contract →
← previous block·next block →recent activity