← previous blocknext block →recent activity
Analyzing
Block #86,617,733
17 transactions · 17 stateful · 2026-07-09 11:52:11 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,617,733 · 17 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
2w03w14w28w39w410w011w512w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x9138a113…0d5f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x4cfe5cde…f2ca
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity