← previous blocknext block →recent activity
Analyzing
Block #86,308,809
16 transactions · 16 stateful · 2026-07-08 01:26:12 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,308,809 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w38w09w111w012w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16778714…a6c9
0x34b655…2a6f
8 touches
6 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
8 touches
6 conflicts
0xd45e7a3b…85f7
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x8c42f949…c9d4
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1d9867ad…6d9a
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 0x16778714af…96a6c9
Audit this contract →
← previous block·next block →recent activity