← previous blocknext block →recent activity
Analyzing
Block #108,402,209
14 transactions · 13 stateful · 2026-09-27 07:11:03 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,402,209 · 14 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
1w04w06w17w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7d295a58…00f7
0xd32edf…ff58
3 touches
1 conflict
0x122a4e67…118d
0x34b655…2a6f
2 touches
0 conflicts
0x19841224…7bb4
0x34b655…2a6f
2 touches
0 conflicts
0x42744667…0b8a
0x34b655…2a6f
2 touches
0 conflicts
0x709ddbfe…21b0
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity