← previous blocknext block →recent activity
Analyzing
Block #91,101,529
21 transactions · 21 stateful · 2026-07-28 16:08:44 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,101,529 · 21 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
2w03w04w15w26w37w08w19w211w312w114w015w118w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0x81141822…a5ce
0x34b655…2a6f
4 touches
1 conflict
0x66a11a3b…0ee9
0xa6afd3…d132
4 touches
1 conflict
0x12e8675a…5157
0x34b655…2a6f
4 touches
1 conflict
0x705ab4ae…0162
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity