← previous blocknext block →recent activity
Analyzing
Block #85,603,280
19 transactions · 16 stateful · 2026-07-04 19:00:15 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,603,280 · 19 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
1w02w13w24w05w18w09w110w211w012w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29c1a140…099f
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x9b2c9ea3…e825
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x94f5fc74…a10d
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 0x29c1a140f5…fc099f
Audit this contract →
← previous block·next block →recent activity