← previous blocknext block →recent activity
Analyzing
Block #91,975,790
16 transactions · 15 stateful · 2026-07-31 17:29:09 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,975,790 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w07w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff3dbbcd…5060
0x34b655…2a6f
4 touches
1 conflict
0x77a99df7…d784
0x851145…3f07
4 touches
1 conflict
0x6ccf5c86…9954
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x32810c72…e6c0
0x34b655…2a6f
4 touches
1 conflict
0x6e6b8ec7…2197
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
1 conflict on slot 0xff3dbbcd67…0c5060
Audit this contract →
← previous block·next block →recent activity