← previous blocknext block →recent activity
Analyzing
Block #85,275,580
13 transactions · 11 stateful · 2026-07-03 06:37:55 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,275,580 · 13 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
1w02w13w26w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de2656d…5bbc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xaadb98e2…512c
0xa6afd3…d132
3 touches
1 conflict
0x75d3f6de…7bd9
0x40c49f…2af0
2 touches
0 conflicts
0x529add3d…ccd3
0x754704…b603
2 touches
0 conflicts
0x58a864a6…57e3
0x754704…b603
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 0x2de2656dd0…a95bbc
Audit this contract →
← previous block·next block →recent activity