← previous blocknext block →recent activity
Analyzing
Block #85,128,796
20 transactions · 18 stateful · 2026-07-02 14:20:06 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,128,796 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w213w114w215w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xd90a674b…29f7
0x34b655…2a6f
6 touches
3 conflicts
0x9fd37234…2731
0x34b655…2a6f
6 touches
3 conflicts
0x40b5f387…a164
0x34b655…2a6f
6 touches
3 conflicts
0xea2644f5…8c97
0x34b655…2a6f
6 touches
3 conflicts
0x4384dd01…4f99
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity