← previous blocknext block →recent activity
Analyzing
Block #91,406,162
16 transactions · 16 stateful · 2026-07-29 17:42:26 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,406,162 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w17w28w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb2195a0c…68ca
0x34b655…2a6f
6 touches
3 conflicts
0x8972e24b…5d77
0x34b655…2a6f
6 touches
3 conflicts
0xd8675136…9a01
0x34b655…2a6f
6 touches
3 conflicts
0xee8b9e9b…f159
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x396b9ce3…21d4
0x34b655…2a6f
6 touches
3 conflicts
0xf5899760…c130
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity