← previous blocknext block →recent activity
Analyzing
Block #91,424,089
6 transactions · 6 stateful · 2026-07-29 19:12:57 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,424,089 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54f0697c…d70c
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x010b6bfe…4581
0x34b655…2a6f
2 touches
0 conflicts
0x017469c4…1562
0x34b655…2a6f
2 touches
0 conflicts
0x0327b211…2766
0x34b655…2a6f
2 touches
0 conflicts
0x0358d223…4714
0x34b655…2a6f
2 touches
0 conflicts
0x089aecdd…92ac
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
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity