← previous blocknext block →recent activity
Analyzing
Block #85,533,678
16 transactions · 14 stateful · 2026-07-04 11:16:36 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,533,678 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w310w412w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x532023a5…d800
0xe52b14…7230
10 touches
10 conflicts
0x8ffa3328…ce11
0xe52b14…7230
10 touches
10 conflicts
0x09a15b10…2639
0x754704…b603
10 touches
10 conflicts
0x5149ba0e…d954
0x754704…b603
10 touches
10 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
10 touches
10 conflicts
0x08fcf623…3513
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity