← previous blocknext block →recent activity
Analyzing
Block #86,511,951
21 transactions · 17 stateful · 2026-07-09 00:03:26 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,511,951 · 21 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
1w02w15w06w17w08w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b8a1f5d…77af
0x40c49f…2af0
2 touches
0 conflicts
0x0c399aea…b339
0x40c49f…2af0
2 touches
0 conflicts
0x6a5b26bd…5aec
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
2 touches
0 conflicts
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
1 conflict on slot 0x5e782d178d…db5318
Audit this contract →
← previous block·next block →recent activity