← previous blocknext block →recent activity
Analyzing
Block #85,179,172
17 transactions · 16 stateful · 2026-07-02 19:55:45 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,179,172 · 17 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
3w04w15w27w28w011w314w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x822f8512…68e0
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb44564d6…bb43
0x34b655…2a6f
6 touches
3 conflicts
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x67f751c1…39ab
0x34b655…2a6f
4 touches
1 conflict
0x949d721f…52c3
0x34b655…2a6f
4 touches
1 conflict
0xb7bef7dc…fdfc
0x34b655…2a6f
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
6 conflicts on slot 0x822f8512e8…4668e0
Audit this contract →
← previous block·next block →recent activity