← previous blocknext block →recent activity
Analyzing
Block #91,244,264
20 transactions · 18 stateful · 2026-07-29 04:06:44 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,244,264 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w09w110w115w216w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac33ff75…077b
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x08a39015…efa0
0x34b655…2a6f
4 touches
1 conflict
0x22bef947…cc48
0x34b655…2a6f
4 touches
1 conflict
0x2f8c826e…c115
0x34b655…2a6f
4 touches
1 conflict
0x313d3d93…4aa2
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: 0xfa32f9ec…fef3f0
1 conflict on slot 0xac33ff75c1…89077b
Audit this contract →
← previous block·next block →recent activity