← previous blocknext block →recent activity
Analyzing
Block #86,075,504
13 transactions · 11 stateful · 2026-07-06 23:28:44 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,075,504 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x3738dde1…e465
0x40c49f…2af0
2 touches
0 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
2 touches
0 conflicts
0x68ebc592…026d
0x40c49f…2af0
2 touches
0 conflicts
0x9af7fe70…3e49
0x40c49f…2af0
2 touches
0 conflicts
0xd2c6a341…f634
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity