← previous blocknext block →recent activity
Analyzing
Block #108,576,397
11 transactions · 11 stateful · 2026-09-27 21:48:03 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,576,397 · 11 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
6w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0x05c53b92…de27
0x34b655…2a6f
4 touches
1 conflict
0x2e502cc4…da44
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9287
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
2 touches
0 conflicts
0xf17982ba…359a
0x34ae4d…3fc5
2 touches
0 conflicts
0xf1fbcd40…9515
0x34ae4d…3fc5
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity