← previous blocknext block →recent activity
Analyzing
Block #91,423,022
16 transactions · 12 stateful · 2026-07-29 19:07:27 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,423,022 · 16 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
6w07w18w29w311w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x418f6232…2de6
0x34b655…2a6f
4 touches
1 conflict
0x051aa260…b0a4
0x34b655…2a6f
2 touches
0 conflicts
0x0ac67576…1cc5
0x34b655…2a6f
2 touches
0 conflicts
0x3076192f…07b1
0x34b655…2a6f
2 touches
0 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity