← previous blocknext block →recent activity
Analyzing
Block #85,344,266
25 transactions · 20 stateful · 2026-07-03 14:15:25 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,344,266 · 25 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
1w02w15w26w08w114w017w018w121w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd06cc746…27e4
0x1001ff…1001
6 touches
3 conflicts
0xd06cc746…27e4
0x91b81b…6d56
6 touches
3 conflicts
0xa159517d…d8d0
0x91b81b…6d56
4 touches
1 conflict
0xa159517d…d8d0
0x1001ff…1001
4 touches
1 conflict
0x3d7c0d06…ca8c
0x188d58…ea8e
4 touches
1 conflict
0x3d7c0d06…ca8e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity