← previous blocknext block →recent activity
Analyzing
Block #91,251,293
16 transactions · 15 stateful · 2026-07-29 04:42:10 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,251,293 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w07w08w19w112w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf7d0a1a5…159a
0x34b655…2a6f
6 touches
3 conflicts
0x347e7e76…914b
0x34b655…2a6f
6 touches
3 conflicts
0xce079a7f…f40b
0x34b655…2a6f
6 touches
3 conflicts
0x50afedcd…91cc
0x34b655…2a6f
6 touches
3 conflicts
0xe4d8276f…32e9
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity