← previous blocknext block →recent activity
Analyzing
Block #91,254,993
7 transactions · 5 stateful · 2026-07-29 05:00:48 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,254,993 · 7 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
2w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6edce976…dedb
0x34b655…2a6f
4 touches
1 conflict
0x7ca2d580…4be4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xf0bf41b6…682f
0x34b655…2a6f
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
2 touches
0 conflicts
0x289b2009…512c
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 0x6edce97614…c9dedb
Audit this contract →
← previous block·next block →recent activity