← previous blocknext block →recent activity
Analyzing
Block #91,086,031
6 transactions · 6 stateful · 2026-07-28 14:50:44 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,086,031 · 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
0x388f7ccb…bb14
0x34b655…2a6f
4 touches
1 conflict
0xa687a4f2…74d1
0x34b655…2a6f
4 touches
1 conflict
0xb78e310b…67f1
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x1664dd20…d2a9
0x34b655…2a6f
2 touches
0 conflicts
0x18e60785…ab8b
0x34b655…2a6f
2 touches
0 conflicts
0x1a917b21…8794
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 0x388f7ccbf1…9abb14
Audit this contract →
← previous block·next block →recent activity