← previous blocknext block →recent activity
Analyzing
Block #85,916,831
8 transactions · 6 stateful · 2026-07-06 05:49:28 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,916,831 · 8 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
2w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d3dac50…4731
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0x9c284468…0c8d
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x36c2bbc0…753a
0x34b655…2a6f
3 touches
1 conflict
0xa966b790…877b
0x34b655…2a6f
3 touches
1 conflict
0x2951ccd8…7ddc
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 0x1d3dac5001…284731
Audit this contract →
← previous block·next block →recent activity