← previous blocknext block →recent activity
Analyzing
Block #85,133,001
19 transactions · 19 stateful · 2026-07-02 14:48:14 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
2.42
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,133,001 · 19 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w59w610w711w817w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191c9934…f4f4
0x34b655…2a6f
18 touches
36 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xa1111a1a…f235
0x34b655…2a6f
18 touches
36 conflicts
0x8ed3945b…b302
0x34b655…2a6f
18 touches
36 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0x701f725b…c923
0x34b655…2a6f
16 touches
28 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
16 touches
28 conflicts
0x7fbb3611…bed3
0x34b655…2a6f
16 touches
28 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
36 conflicts on slot 0x191c9934e4…8cf4f4
Audit this contract →
← previous block·next block →recent activity