← previous blocknext block →recent activity
Analyzing
Block #86,709,048
17 transactions · 13 stateful · 2026-07-09 22:03:07 UTC
Parallelism
53/100
Blocked
54%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,709,048 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x30c0aa06…d479
0x34b655…2a6f
4 touches
1 conflict
0x38a6ef6a…4fee
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x66edb904…1982
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity