← previous blocknext block →recent activity
Analyzing
Block #91,109,688
21 transactions · 17 stateful · 2026-07-28 16:49:46 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,109,688 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w19w210w012w213w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf30b9357…2e1e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
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: 0x80c74517…647210
3 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity