← previous blocknext block →recent activity
Analyzing
Block #86,815,436
17 transactions · 15 stateful · 2026-07-10 09:53:49 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,815,436 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w210w311w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00873542…6db6
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x66721b6c…84e8
0x34b655…2a6f
4 touches
1 conflict
0x73a951a2…53db
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf5042875…9a93
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
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
3 conflicts on slot 0x00873542d7…d96db6
Audit this contract →
← previous block·next block →recent activity