← previous blocknext block →recent activity
Analyzing
Block #86,216,761
39 transactions · 29 stateful · 2026-07-07 15:11:36 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,216,761 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w19w210w311w423w224w425w526w327w528w629w731w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
10 touches
10 conflicts
0x202c03eb…cf33
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity