← previous blocknext block →recent activity
Analyzing
Block #91,418,175
17 transactions · 16 stateful · 2026-07-29 18:43:05 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,418,175 · 17 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
2w03w14w25w36w48w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xaa388e50…f062
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0003
0x48cba2…b48b
2 touches
0 conflicts
0xa50eece0…1634
0x73e064…0148
2 touches
0 conflicts
0x3ed47319…089d
0x754704…b603
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: 0x48cba278…e2b48b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity