← previous blocknext block →recent activity
Analyzing
Block #108,533,960
24 transactions · 20 stateful · 2026-09-27 18:14:14 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,533,960 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w016w117w218w322w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x5acd9e7b…2eb2
0x34b655…2a6f
4 touches
1 conflict
0x6c09658a…d1d9
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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity