← previous blocknext block →recent activity
Analyzing
Block #85,129,206
22 transactions · 19 stateful · 2026-07-02 14:22:51 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,129,206 · 22 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
1w02w14w010w113w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x66c5e348…51d0
0xa6afd3…d132
4 touches
1 conflict
0x1b3114cd…5e2d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x37421b44…45b5
0x34b655…2a6f
4 touches
1 conflict
0x6a53b1c0…c3f2
0x34b655…2a6f
4 touches
1 conflict
0x942cf72c…efa9
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity