← previous blocknext block →recent activity
Analyzing
Block #86,049,533
13 transactions · 11 stateful · 2026-07-06 20:35:32 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,049,533 · 13 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
1w02w19w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x141c490e…8343
0x34b655…2a6f
6 touches
3 conflicts
0x76409f96…0ca6
0x34b655…2a6f
5 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x457f0e04…534e
0x34b655…2a6f
4 touches
1 conflict
0x4696bc48…e21a
0x34b655…2a6f
4 touches
1 conflict
0x54a035dd…16c6
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity