← previous blocknext block →recent activity
Analyzing
Block #86,245,008
39 transactions · 32 stateful · 2026-07-07 18:20:15 UTC
Parallelism
87/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,245,008 · 39 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
1w02w14w17w29w010w011w112w213w315w316w424w428w430w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x050dc515…5d4a
0xd32edf…ff58
9 touches
10 conflicts
0x1e9a8e72…7138
0x43cf54…7777
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
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: USDC (USDC)
10 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity