← previous blocknext block →recent activity
Analyzing
Block #85,544,804
15 transactions · 12 stateful · 2026-07-04 12:30:42 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,544,804 · 15 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
1w06w09w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x379060ba…5ee7
0x065c9d…c394
3 touches
1 conflict
0xc077ee51…bc27
0x065c9d…c394
3 touches
1 conflict
0x567b2d2f…5af8
0x065c9d…c394
2 touches
0 conflicts
0xb91ec5bb…f312
0x065c9d…c394
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity