← previous blocknext block →recent activity
Analyzing
Block #85,181,619
19 transactions · 16 stateful · 2026-07-02 20:12:05 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,181,619 · 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
1w02w13w04w15w26w38w215w016w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x744e0a36…70f7
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x086db8fc…0024
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x20079932…08b5
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x744e0a3655…6d70f7
Audit this contract →
← previous block·next block →recent activity