← previous blocknext block →recent activity
Analyzing
Block #86,350,964
10 transactions · 10 stateful · 2026-07-08 06:07:44 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,350,964 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcb83a555…f6c0
0x065c9d…c394
4 touches
1 conflict
0xb4aa41e0…f123
0x34b655…2a6f
4 touches
1 conflict
0x1f0ad9ae…1b26
0x065c9d…c394
3 touches
1 conflict
0x98c07e30…9a39
0x065c9d…c394
2 touches
0 conflicts
0xae3ffe20…b12b
0x065c9d…c394
2 touches
0 conflicts
0xbdfb7631…e6c6
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity