← previous blocknext block →recent activity
Analyzing
Block #91,260,570
16 transactions · 14 stateful · 2026-07-29 05:28:52 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,260,570 · 16 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
1w02w13w27w38w410w011w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b4c6644…32f6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
6 touches
3 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
6 touches
3 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x64420f3d…07e3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x5b4c664429…c332f6
Audit this contract →
← previous block·next block →recent activity