← previous blocknext block →recent activity
Analyzing
Block #86,914,973
19 transactions · 14 stateful · 2026-07-10 20:59:29 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,914,973 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6cbda8c…83c8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xfe0c34c7…76b0
0x34b655…2a6f
4 touches
1 conflict
0xfe0c34c7…76b1
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x1f6a9f37…e6d5
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0xe6cbda8c19…b183c8
Audit this contract →
← previous block·next block →recent activity