← previous blocknext block →recent activity
Analyzing
Block #86,214,644
38 transactions · 27 stateful · 2026-07-07 14:57:26 UTC
Parallelism
84/100
Blocked
59%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,214,644 · 38 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w08w19w217w018w119w221w022w224w325w226w327w128w129w330w431w134w336w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity