← previous blocknext block →recent activity
Analyzing
Block #91,386,087
13 transactions · 10 stateful · 2026-07-29 16:01:17 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,386,087 · 13 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
2w03w18w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf93de73e…5fe0
0xd32edf…ff58
5 touches
3 conflicts
0xd33ebcd0…9f7e
0x34b655…2a6f
4 touches
1 conflict
0x340ec029…3c44
0x34b655…2a6f
4 touches
1 conflict
0x6c41c65c…7815
0x34b655…2a6f
4 touches
1 conflict
0x9807e413…7362
0x34b655…2a6f
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0xa1087a5c…66c4
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity