← previous blocknext block →recent activity
Analyzing
Block #86,903,834
27 transactions · 22 stateful · 2026-07-10 19:45:02 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,903,834 · 27 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
1w02w13w24w36w07w08w111w114w016w018w119w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61d65579…ee3c
0xad96c3…8d7c
8 touches
6 conflicts
0x00000000…0008
0x86dbf0…eb2d
8 touches
6 conflicts
0xd821cffd…3ff0
0x754704…b603
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x56a919c4…ab49
0xad96c3…8d7c
6 touches
3 conflicts
0x59c33cee…7bbe
0xd32edf…ff58
5 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0xad96c3df…cc8d7c
6 conflicts on slot 0x61d655794f…24ee3c
Audit this contract →
← previous block·next block →recent activity