← previous blocknext block →recent activity
Analyzing
Block #108,446,466
16 transactions · 11 stateful · 2026-09-27 10:53:48 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,446,466 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518b8dce…6d60
0x34b655…2a6f
6 touches
3 conflicts
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x5e6d5ed2…341f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x829a760f…5e55
0x34b655…2a6f
4 touches
1 conflict
0x87b3c188…6ea2
0x34b655…2a6f
4 touches
1 conflict
0x3ba7edbb…80e6
0x34ae4d…3fc5
2 touches
0 conflicts
0x53e50026…6d8c
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
3 conflicts on slot 0x518b8dce2e…7e6d60
Audit this contract →
← previous block·next block →recent activity