← previous blocknext block →recent activity
Analyzing
Block #108,494,426
16 transactions · 16 stateful · 2026-09-27 14:55:13 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,494,426 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w311w413w014w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
10 touches
10 conflicts
0x16d77246…bac5
0x34b655…2a6f
6 touches
3 conflicts
0x206c55db…94ea
0x34b655…2a6f
6 touches
3 conflicts
0x274a8f8b…3603
0x34b655…2a6f
6 touches
3 conflicts
0x280aaa58…1c52
0x34b655…2a6f
6 touches
3 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
6 touches
3 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity