← previous blocknext block →recent activity
Analyzing
Block #109,234,488
17 transactions · 15 stateful · 2026-09-30 05:07:35 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #109,234,488 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca713a35…abfd
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x10a1726d…3719
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x3f8eaaff…dad5
0x34b655…2a6f
2 touches
0 conflicts
0x6886fa66…069d
0x34b655…2a6f
2 touches
0 conflicts
0x7c16d507…9ab9
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xca713a3595…59abfd
Audit this contract →
← previous block·next block →recent activity