← previous blocknext block →recent activity
Analyzing
Block #86,298,809
27 transactions · 25 stateful · 2026-07-08 00:19:23 UTC
Parallelism
89/100
Blocked
52%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,298,809 · 27 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w09w110w112w213w014w116w217w118w019w120w021w122w224w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x18a2828a…26dd
0x40c49f…2af0
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0xf3e21855…a464
0xd32edf…ff58
5 touches
3 conflicts
0x0db0aaac…e94d
0x43cf54…7777
4 touches
1 conflict
0x5504f74a…6874
0x43cf54…7777
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 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity