← previous blocknext block →recent activity
Analyzing
Block #109,056,730
24 transactions · 23 stateful · 2026-09-29 14:12:02 UTC
Parallelism
54/100
Blocked
57%
Avg conflicts / tx
2.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #109,056,730 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w516w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4550172…3d03
0x34b655…2a6f
18 touches
36 conflicts
0xfc8c9734…8019
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xd275ed99…2e99
0x34b655…2a6f
12 touches
15 conflicts
0xdd9dc4b3…73b8
0x34b655…2a6f
12 touches
15 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
12 touches
15 conflicts
0x238d0a65…428b
0x37db7f…ec7b
12 touches
15 conflicts
0x18861dbf…968e
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0xc4550172b5…c13d03
Audit this contract →
← previous block·next block →recent activity