← previous blocknext block →recent activity
Analyzing
Block #86,298,691
20 transactions · 19 stateful · 2026-07-08 00:18:36 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,298,691 · 20 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
2w04w05w18w29w210w111w013w314w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x224bab73…a729
0x34b655…2a6f
4 touches
1 conflict
0x32adb2c4…32c5
0x34b655…2a6f
4 touches
1 conflict
0x336fbcc7…60a7
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity