← previous blocknext block →recent activity
Analyzing
Block #109,004,286
21 transactions · 19 stateful · 2026-09-29 09:47:06 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,004,286 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w09w110w411w214w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0xff113b60…7d71
0xd32edf…ff58
7 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x68a6938f…55c8
0x34b655…2a6f
6 touches
3 conflicts
0x724ba0cf…01c7
0x34b655…2a6f
6 touches
3 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
6 touches
3 conflicts
0x88fc2a68…3918
0x34b655…2a6f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity