← previous blocknext block →recent activity
Analyzing
Block #91,253,509
9 transactions · 9 stateful · 2026-07-29 04:53:19 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,253,509 · 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
1w02w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eb3e5af…064e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x629b0769…1150
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x9927f045…9256
0x34b655…2a6f
4 touches
1 conflict
0x9a89094e…f5b2
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 0x6eb3e5af4f…78064e
Audit this contract →
← previous block·next block →recent activity