← previous blocknext block →recent activity
Analyzing
Block #85,191,235
19 transactions · 15 stateful · 2026-07-02 21:16:04 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,191,235 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w310w012w413w115w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x833ebd97…5abb
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x66c5e348…51d0
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
3 conflicts on slot 0x833ebd9703…2b5abb
Audit this contract →
← previous block·next block →recent activity