← previous blocknext block →recent activity
Analyzing
Block #85,170,241
22 transactions · 19 stateful · 2026-07-02 18:56:18 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,170,241 · 22 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
2w03w15w27w38w09w110w211w312w414w016w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd25a34fd…3e4d
0x34b655…2a6f
10 touches
10 conflicts
0xa457c06e…2f06
0x34b655…2a6f
8 touches
6 conflicts
0x3a395c73…35de
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xbdc99210…6765
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x6113f066…3029
0x34b655…2a6f
8 touches
6 conflicts
0x16b3a441…13db
0x34b655…2a6f
8 touches
6 conflicts
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 0xd25a34fd71…9c3e4d
Audit this contract →
← previous block·next block →recent activity