← previous blocknext block →recent activity
Analyzing
Block #86,608,893
23 transactions · 19 stateful · 2026-07-09 10:53:11 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,608,893 · 23 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
2w09w112w017w118w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0x92fcdf1e…23a7
0x34b655…2a6f
5 touches
3 conflicts
0xd5e6e5ee…9fb2
0x34b655…2a6f
4 touches
1 conflict
0x29a5ecc7…7df7
0x851145…3f07
4 touches
1 conflict
0x32aa281b…0f8e
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