← previous blocknext block →recent activity
Analyzing
Block #86,492,900
29 transactions · 24 stateful · 2026-07-08 21:56:24 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,492,900 · 29 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
1w02w14w06w09w010w111w212w215w116w318w121w427w028w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57bb625a…286d
0x34b655…2a6f
8 touches
6 conflicts
0x31723dcf…4e92
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x284bb696…4091
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0f8965bb…e238
0x34b655…2a6f
4 touches
1 conflict
0x5f34fd08…aeb3
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 0x57bb625a4b…6d286d
Audit this contract →
← previous block·next block →recent activity