← previous blocknext block →recent activity
Analyzing
Block #91,163,958
15 transactions · 15 stateful · 2026-07-28 21:22:46 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,163,958 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x811cb01f…e507
0x34b655…2a6f
6 touches
3 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
6 touches
3 conflicts
0xce449340…7db1
0x34b655…2a6f
6 touches
3 conflicts
0x5a2f19ef…f94e
0x34b655…2a6f
6 touches
3 conflicts
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x755b0df4…f57e
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity