← previous blocknext block →recent activity
Analyzing
Block #91,125,649
18 transactions · 16 stateful · 2026-07-28 18:10:04 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,125,649 · 18 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
2w03w14w15w210w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ca3397e…3644
0x34b655…2a6f
4 touches
1 conflict
0x0f69f34e…c78e
0x34b655…2a6f
4 touches
1 conflict
0x322fa8a2…7d2d
0x34b655…2a6f
4 touches
1 conflict
0x45cd503b…4d50
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x8620aea9…e23c
0x34b655…2a6f
4 touches
1 conflict
0x8cb33e96…1609
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
1 conflict on slot 0x0ca3397e4c…4c3644
Audit this contract →
← previous block·next block →recent activity