← previous blocknext block →recent activity
Analyzing
Block #86,690,843
34 transactions · 25 stateful · 2026-07-09 20:01:41 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,690,843 · 34 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
7w020w122w226w329w030w131w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa81573d5…7571
0xd32edf…ff58
5 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x05e83dc2…b7a0
0x34b655…2a6f
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x11560115…bfc2
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
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