← previous blocknext block →recent activity
Analyzing
Block #85,919,017
21 transactions · 19 stateful · 2026-07-06 06:04:02 UTC
Parallelism
67/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,919,017 · 21 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
4w05w110w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x604accd8…f993
0x34b655…2a6f
4 touches
1 conflict
0x6c595e56…d5ff
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity