← previous blocknext block →recent activity
Analyzing
Block #108,566,135
17 transactions · 17 stateful · 2026-09-27 20:56:25 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,566,135 · 17 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
1w02w13w25w06w19w010w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x4aa8b305…4ace
0x860869…ff01
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x231e0ffc…0b1a
0x34b655…2a6f
4 touches
1 conflict
0x28e2f7c3…e848
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity