← previous blocknext block →recent activity
Analyzing
Block #85,272,954
22 transactions · 21 stateful · 2026-07-03 06:20:23 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,272,954 · 22 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
6w09w010w011w112w213w117w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xba46b844…c049
0x34b655…2a6f
6 touches
3 conflicts
0x6f1bd077…2005
0x34b655…2a6f
6 touches
3 conflicts
0x4ef263bb…fcf0
0x34b655…2a6f
6 touches
3 conflicts
0x622c94c8…d2c4
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x905dbe77…bf05
0xa6afd3…d132
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity