← previous blocknext block →recent activity
Analyzing
Block #86,239,771
24 transactions · 21 stateful · 2026-07-07 17:45:13 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,239,771 · 24 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
2w05w06w17w210w114w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
10 touches
10 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
6 touches
3 conflicts
0x4bc0441e…58bb
0x34b655…2a6f
6 touches
3 conflicts
0xbd9491f7…dd92
0x34b655…2a6f
6 touches
3 conflicts
0xbfa73fac…6fff
0x34b655…2a6f
6 touches
3 conflicts
0xd6479834…4e61
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity