← previous blocknext block →recent activity
Analyzing
Block #108,611,606
40 transactions · 33 stateful · 2026-09-28 00:45:18 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,611,606 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w39w412w513w217w618w719w821w933w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0xe7999424…312f
0xd32edf…ff58
7 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x03624810…e26d
0x34b655…2a6f
6 touches
3 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity