← previous blocknext block →recent activity
Analyzing
Block #109,064,875
35 transactions · 23 stateful · 2026-09-29 14:53:05 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
0.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,064,875 · 35 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
1w02w13w25w26w37w08w112w416w318w220w329w432w533w634w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xcc190dcf…0c72
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x116fb54f…dd28
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity