← previous blocknext block →recent activity
Analyzing
Block #85,989,299
24 transactions · 21 stateful · 2026-07-06 13:53:02 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,989,299 · 24 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
2w09w110w011w115w016w117w218w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd40bddc1…773c
0x34b655…2a6f
6 touches
3 conflicts
0x7d2645cd…5d8e
0x34b655…2a6f
6 touches
3 conflicts
0xb245fe36…d765
0x34b655…2a6f
6 touches
3 conflicts
0x3bdab090…c5bf
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x5a8b47f0…7fbd
0x34b655…2a6f
4 touches
1 conflict
0x85a88798…f85e
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity