← previous blocknext block →recent activity
Analyzing
Block #86,232,365
19 transactions · 16 stateful · 2026-07-07 16:55:47 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,232,365 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w011w212w114w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x76634d89…e763
0x34b655…2a6f
4 touches
1 conflict
0x99c093c1…9cd0
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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity