← previous blocknext block →recent activity
Analyzing
Block #86,485,074
23 transactions · 23 stateful · 2026-07-08 21:04:09 UTC
Parallelism
87/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,485,074 · 23 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
2w05w06w17w29w012w114w215w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f24a374…6bc3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9f3e922c…891f
0x40c49f…2af0
4 touches
1 conflict
0xa775fccb…4e8f
0x40c49f…2af0
4 touches
1 conflict
0xf1f11c8a…7f7b
0x40c49f…2af0
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 0x3f24a37442…3c6bc3
Audit this contract →
← previous block·next block →recent activity