← previous blocknext block →recent activity
Analyzing
Block #85,671,229
28 transactions · 25 stateful · 2026-07-05 02:32:31 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,671,229 · 28 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
1w02w16w17w08w112w013w114w215w016w217w118w321w122w223w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x56f59993…2c32
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x49d02518…ca01
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xca0f0668…caf3
0xa6afd3…d132
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity