← previous blocknext block →recent activity
Analyzing
Block #108,961,032
24 transactions · 21 stateful · 2026-09-29 06:08:26 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,961,032 · 24 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
2w03w14w25w39w410w511w615w417w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xa7199234…a277
0x34b655…2a6f
8 touches
6 conflicts
0x238d0a65…428b
0x37db7f…ec7b
6 touches
3 conflicts
0xfc8c9734…8019
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x88fc2a68…3918
0x34b655…2a6f
6 touches
3 conflicts
0xa4bc6fc4…1f64
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
21 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity