← previous blocknext block →recent activity
Analyzing
Block #85,993,331
34 transactions · 22 stateful · 2026-07-06 14:20:02 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,993,331 · 34 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
4w08w011w117w121w222w124w027w228w231w132w233w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x9da6e429…074d
0xa6afd3…d132
6 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
6 touches
3 conflicts
0x75fad718…6932
0x851145…3f07
4 touches
1 conflict
0xe03c7ec8…cd09
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x59645a97…3ca1
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