← previous blocknext block →recent activity
Analyzing
Block #91,543,723
18 transactions · 16 stateful · 2026-07-30 05:15:37 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,543,723 · 18 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
1w02w14w210w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
8 touches
6 conflicts
0x162f5e54…ef30
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xbb4fd99a…afa6
0x34b655…2a6f
6 touches
3 conflicts
0xe2f7e186…0e54
0xd32edf…ff58
5 touches
3 conflicts
0x57330c5d…9973
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity