← previous blocknext block →recent activity
Analyzing
Block #86,989,360
13 transactions · 11 stateful · 2026-07-11 05:16:31 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,989,360 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c7e1952…d9c9
0x34b655…2a6f
4 touches
1 conflict
0x135cdc1d…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x8d0d8061…d410
0xc8689a…ee79
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x069d0339…72ef
0x34b655…2a6f
2 touches
0 conflicts
0x14c5407b…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x15c330b0…a910
0x34b655…2a6f
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
1 conflict on slot 0x6c7e195218…27d9c9
Audit this contract →
← previous block·next block →recent activity