← previous blocknext block →recent activity
Analyzing
Block #108,539,951
27 transactions · 24 stateful · 2026-09-27 18:44:23 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,539,951 · 27 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
1w02w13w04w15w26w311w012w113w217w018w122w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cf0cbef…f0dc
0x34b655…2a6f
8 touches
6 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
8 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x7f8e3158…9dfd
0x34b655…2a6f
8 touches
6 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
8 touches
6 conflicts
0x9b4d6ea9…30f5
0x34b655…2a6f
8 touches
6 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x0cf0cbeffd…75f0dc
Audit this contract →
← previous block·next block →recent activity