← previous blocknext block →recent activity
Analyzing
Block #91,135,991
19 transactions · 16 stateful · 2026-07-28 19:02:05 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,135,991 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w111w012w213w114w316w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0xd676e291…3ecf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdd190722…ecae
0x34b655…2a6f
6 touches
3 conflicts
0x0f3152e8…f181
0x34b655…2a6f
4 touches
1 conflict
0x1113d57f…70fb
0x34b655…2a6f
4 touches
1 conflict
0x1a5becdb…56f9
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
6 conflicts on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity