← previous blocknext block →recent activity
Analyzing
Block #86,231,996
13 transactions · 11 stateful · 2026-07-07 16:53:19 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,231,996 · 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
2w03w14w07w110w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0bdc62a4…13f9
0x34b655…2a6f
2 touches
0 conflicts
0x109bd42b…f54d
0x34b655…2a6f
2 touches
0 conflicts
0x15190be9…97ec
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity