← previous blocknext block →recent activity
Analyzing
Block #91,404,794
8 transactions · 6 stateful · 2026-07-29 17:35:29 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,404,794 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0xad2bb81f…4d6b
0x34b655…2a6f
4 touches
1 conflict
0xb4b03a70…7c86
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x141e63c5…f9c8
0x34b655…2a6f
2 touches
0 conflicts
0x312e4698…54c0
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
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
1 conflict on slot 0x0a0cecef55…324ed0
Audit this contract →
← previous block·next block →recent activity