← previous blocknext block →recent activity
Analyzing
Block #86,307,077
10 transactions · 8 stateful · 2026-07-08 01:14:36 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,307,077 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
4 touches
1 conflict
0x8d0d8061…d410
0xc8689a…ee79
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8c42f949…c9d4
0x851145…3f07
4 touches
1 conflict
0x93d4b4e9…5daa
0x851145…3f07
4 touches
1 conflict
0x0fc92f7d…9122
0x851145…3f07
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
3 conflicts on slot 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity