← previous blocknext block →recent activity
Analyzing
Block #108,532,169
24 transactions · 22 stateful · 2026-09-27 18:05:13 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,532,169 · 24 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
2w04w05w17w113w218w219w222w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9806b4d…9587
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x74851f5e…fadd
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xcfb7a478…6d32
0xd32edf…ff58
5 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
0x34b655…2a6f
4 touches
1 conflict
0x2d4fb793…b3de
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 0xe9806b4da4…749587
Audit this contract →
← previous block·next block →recent activity