← previous blocknext block →recent activity
Analyzing
Block #86,315,067
19 transactions · 16 stateful · 2026-07-08 02:08:02 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,315,067 · 19 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
1w02w03w15w07w19w012w214w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99701186…1cbf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xed2b4fc7…6963
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f2db81d…e778
0x34b655…2a6f
4 touches
1 conflict
0x8eb1bf52…3ee4
0x34b655…2a6f
4 touches
1 conflict
0xd4726587…6289
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
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
3 conflicts on slot 0x997011860a…ad1cbf
Audit this contract →
← previous block·next block →recent activity