← previous blocknext block →recent activity
Analyzing
Block #85,826,929
12 transactions · 11 stateful · 2026-07-05 19:50:36 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,826,929 · 12 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5681747…c048
0xe1c8b7…3022
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x585836d5…5043
0x9f3832…4ae4
8 touches
6 conflicts
0x585836d5…5044
0x9f3832…4ae4
8 touches
6 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
8 touches
6 conflicts
0xd4e43528…777e
0x9f3832…4ae4
8 touches
6 conflicts
0x67d846dd…358c
0xc5db38…7777
8 touches
6 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: 0xe1c8b733…e33022
6 conflicts on slot 0xb568174725…c6c048
Audit this contract →
← previous block·next block →recent activity