← previous blocknext block →recent activity
Analyzing
Block #85,130,204
21 transactions · 18 stateful · 2026-07-02 14:29:31 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,130,204 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w19w010w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x85631114…3ff6
0xa6afd3…d132
6 touches
3 conflicts
0x12c6929d…e7db
0x34b655…2a6f
6 touches
3 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0xfbe7d5a7…9ff1
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: 0x69df8a43…506292
3 conflicts on slot 0xdb06702604…0f9eb8
Audit this contract →
← previous block·next block →recent activity