← previous blocknext block →recent activity
Analyzing
Block #91,984,511
36 transactions · 35 stateful · 2026-07-31 18:13:01 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,984,511 · 36 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
2w03w04w16w19w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f05abc0…94bd
0x34b655…2a6f
8 touches
6 conflicts
0x641aed07…bcb9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x90e459b7…31c2
0x34b655…2a6f
6 touches
3 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0x753b2da4…7a6d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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 0x9f05abc0b2…2994bd
Audit this contract →
← previous block·next block →recent activity