← previous blocknext block →recent activity
Analyzing
Block #91,297,912
13 transactions · 10 stateful · 2026-07-29 08:37:32 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,297,912 · 13 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
1w05w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf862728a…c2bf
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5cc0e9c8…3ae6
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 0xf862728a40…46c2bf
Audit this contract →
← previous block·next block →recent activity