← previous blocknext block →recent activity
Analyzing
Block #108,576,938
19 transactions · 17 stateful · 2026-09-27 21:50:46 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,576,938 · 19 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
2w03w16w27w39w010w311w112w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05c53b92…de27
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe4de06ee…61f3
0x34b655…2a6f
4 touches
1 conflict
0xc1cff71d…4808
0x34b655…2a6f
4 touches
1 conflict
0xc2374606…93f7
0x34b655…2a6f
4 touches
1 conflict
0xc2fe6ed6…f8be
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0x0902c705…9d3b
0x34b655…2a6f
4 touches
1 conflict
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 0x05c53b9281…cfde27
Audit this contract →
← previous block·next block →recent activity