← previous blocknext block →recent activity
Analyzing
Block #91,969,406
30 transactions · 26 stateful · 2026-07-31 16:57:03 UTC
Parallelism
83/100
Blocked
54%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,969,406 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w08w19w010w111w212w013w114w215w316w017w118w019w120w321w426w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x3de775b2…319b
0xa6afd3…d132
8 touches
6 conflicts
0xfa551be3…a911
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1b49b083…91d8
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity