← previous blocknext block →recent activity
Analyzing
Block #91,417,183
13 transactions · 13 stateful · 2026-07-29 18:38:05 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,417,183 · 13 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
5w07w18w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0xc7ea2751…3347
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5e60bc…fe22
2 touches
0 conflicts
0x00000000…0004
0x5e60bc…fe22
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
1 conflict on slot 0xcb89a8187c…8fe7c1
Audit this contract →
← previous block·next block →recent activity