← previous blocknext block →recent activity
Analyzing
Block #109,176,155
22 transactions · 21 stateful · 2026-09-30 00:13:59 UTC
Parallelism
64/100
Blocked
62%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,176,155 · 22 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
2w03w14w25w27w39w310w413w417w418w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x4cfc94f9…ca97
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0053
0x1b6862…e19c
8 touches
6 conflicts
0x1d5648b1…c329
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity