← previous blocknext block →recent activity
Analyzing
Block #85,146,690
23 transactions · 20 stateful · 2026-07-02 16:19:32 UTC
Parallelism
87/100
Blocked
25%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,146,690 · 23 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
2w03w04w15w06w08w19w215w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x264f7d7d…8444
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x28247a23…348b
0x065c9d…c394
4 touches
1 conflict
0x60439a27…9cb1
0x065c9d…c394
4 touches
1 conflict
0x8a7fb840…96ad
0x065c9d…c394
4 touches
1 conflict
0xf9d72263…3ced
0x065c9d…c394
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity