← previous blocknext block →recent activity
Analyzing
Block #86,231,058
29 transactions · 22 stateful · 2026-07-07 16:47:04 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,231,058 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w09w110w115w216w018w219w321w023w324w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x8a2f9a36…fb4a
0xfa32f9…f3f0
6 touches
3 conflicts
0x6d307d38…f2e9
0xd32edf…ff58
5 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
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: 0xfa32f9ec…fef3f0
3 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity