← previous blocknext block →recent activity
Analyzing
Block #85,193,626
19 transactions · 16 stateful · 2026-07-02 21:31:58 UTC
Parallelism
84/100
Blocked
25%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,193,626 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w18w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
6 touches
3 conflicts
0xc2bb169a…dec2
0x065c9d…c394
5 touches
3 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
4 touches
1 conflict
0x36d04d61…ee9d
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc8c39eb0…38c9
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
3 conflicts on slot 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity