← previous blocknext block →recent activity
Analyzing
Block #109,176,366
42 transactions · 34 stateful · 2026-09-30 00:15:03 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,176,366 · 42 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
1w03w05w06w07w18w19w010w111w112w014w017w118w119w222w125w326w230w232w035w137w338w441w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xdaf3366d…802b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0xab2a87f1…eafd
0x1b6862…e19c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity