← previous blocknext block →recent activity
Analyzing
Block #91,250,001
18 transactions · 15 stateful · 2026-07-29 04:35:39 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,250,001 · 18 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
1w02w13w04w16w07w18w114w215w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1526b11f…8b21
0x34b655…2a6f
6 touches
3 conflicts
0x6847107a…f468
0xa6afd3…d132
4 touches
1 conflict
0xa0d3faac…ae01
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2491d756…b71c
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0x1526b11fec…5a8b21
Audit this contract →
← previous block·next block →recent activity