← previous blocknext block →recent activity
Analyzing
Block #91,240,894
8 transactions · 6 stateful · 2026-07-29 03:49:47 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,240,894 · 8 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
1w04w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32b7e349…5f63
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x10f0c85b…071b
0x34b655…2a6f
2 touches
0 conflicts
0x63a65236…d9a9
0x34b655…2a6f
2 touches
0 conflicts
0x7624b9d6…59e6
0x34b655…2a6f
2 touches
0 conflicts
0x76ed8777…1e5f
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 0x32b7e34965…585f63
Audit this contract →
← previous block·next block →recent activity