← previous blocknext block →recent activity
Analyzing
Block #109,004,399
37 transactions · 34 stateful · 2026-09-29 09:47:42 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,004,399 · 37 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
1w02w13w04w05w06w17w08w19w010w213w014w115w216w318w220w326w227w328w429w330w434w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc464a0a8…bae7
0x34b655…2a6f
8 touches
6 conflicts
0x66fc0764…05fd
0x34b655…2a6f
8 touches
6 conflicts
0x0e303d2c…8574
0xd32edf…ff58
7 touches
6 conflicts
0x6235638c…643c
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity