← previous blocknext block →recent activity
Analyzing
Block #85,136,594
16 transactions · 15 stateful · 2026-07-02 15:12:11 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,136,594 · 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
2w03w14w05w16w27w38w413w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa99c369…263d
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x0085eaee…a96e
0x34b655…2a6f
6 touches
3 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe47478a3…a058
0x34b655…2a6f
6 touches
3 conflicts
0x353d9082…4d53
0x34b655…2a6f
6 touches
3 conflicts
0x0ea744b8…dd30
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
10 conflicts on slot 0xaa99c36928…4d263d
Audit this contract →
← previous block·next block →recent activity