← previous blocknext block →recent activity
Analyzing
Block #91,545,364
9 transactions · 8 stateful · 2026-07-30 05:23:52 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,545,364 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x021df0f6…5d6f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0x021df0f60a…0e5d6f
Audit this contract →
← previous block·next block →recent activity