← previous blocknext block →recent activity
Analyzing
Block #108,510,423
21 transactions · 17 stateful · 2026-09-27 16:15:46 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,510,423 · 21 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
6w08w19w110w211w312w418w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3f7a1de…43e1
0x34b655…2a6f
6 touches
3 conflicts
0x6eda9197…791d
0x34b655…2a6f
6 touches
3 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
6 touches
3 conflicts
0xcedcf390…eeeb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0xdd77da90…6df4
0x34b655…2a6f
4 touches
1 conflict
0x74851f5e…fadd
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 0xb3f7a1de3d…e943e1
Audit this contract →
← previous block·next block →recent activity