← previous blocknext block →recent activity
Analyzing
Block #86,361,045
24 transactions · 23 stateful · 2026-07-08 07:15:03 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,361,045 · 24 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
1w02w03w17w110w011w012w013w014w115w216w320w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x5375bb6c…50ca
0x40c49f…2af0
6 touches
3 conflicts
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xc5e57aea…6ff8
0x34b655…2a6f
4 touches
1 conflict
0xcc58c80b…ff79
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity