← previous blocknext block →recent activity
Analyzing
Block #85,215,912
21 transactions · 16 stateful · 2026-07-03 00:00:25 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,215,912 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w08w110w214w316w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xb04d17a0…10e8
0x34b655…2a6f
4 touches
1 conflict
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity