← previous blocknext block →recent activity
Analyzing
Block #91,972,429
27 transactions · 23 stateful · 2026-07-31 17:12:15 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,972,429 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w110w011w112w213w314w115w416w521w222w524w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x2ab05d5b…0953
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3de775b2…319b
0xa6afd3…d132
6 touches
3 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x634549fe…c16b
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
15 conflicts on slot 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity