← previous blocknext block →recent activity
Analyzing
Block #91,385,667
35 transactions · 24 stateful · 2026-07-29 15:59:10 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,385,667 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w111w219w020w121w222w323w424w525w326w028w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3c676c1…bb6c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3b9bb58c…e73a
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 0xa3c676c125…62bb6c
Audit this contract →
← previous block·next block →recent activity