← previous blocknext block →recent activity
Analyzing
Block #85,875,221
22 transactions · 16 stateful · 2026-07-06 01:12:16 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,875,221 · 22 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
1w02w13w25w37w48w09w110w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f5d8f7e…6f56
0x851145…3f07
8 touches
6 conflicts
0x2d9ecc9e…5a04
0x851145…3f07
8 touches
6 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0x915c095e…c1e5
0x69df8a…6292
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
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: 0x851145ea…9f3f07
6 conflicts on slot 0x4f5d8f7e68…396f56
Audit this contract →
← previous block·next block →recent activity