← previous blocknext block →recent activity
Analyzing
Block #86,453,890
18 transactions · 17 stateful · 2026-07-08 17:35:27 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,453,890 · 18 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
1w02w13w04w17w18w210w315w416w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b628349…f327
0x34b655…2a6f
8 touches
6 conflicts
0xc943e206…97fd
0x34b655…2a6f
6 touches
3 conflicts
0x092832cd…7b28
0x34b655…2a6f
6 touches
3 conflicts
0x469e824a…d814
0x34b655…2a6f
6 touches
3 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
6 touches
3 conflicts
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x3b6e959d…158f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x4b62834977…7ff327
Audit this contract →
← previous block·next block →recent activity