← previous blocknext block →recent activity
Analyzing
Block #91,387,481
8 transactions · 7 stateful · 2026-07-29 16:08:17 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,387,481 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x16b73851…e01d
0x34b655…2a6f
4 touches
1 conflict
0x396f7bac…cf1a
0x34b655…2a6f
4 touches
1 conflict
0x42a656be…6555
0x34b655…2a6f
4 touches
1 conflict
0x447c249a…b42c
0x34b655…2a6f
4 touches
1 conflict
0x4c0627bd…f5c3
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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
3 conflicts on slot 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity