← previous blocknext block →recent activity
Analyzing
Block #86,487,821
14 transactions · 10 stateful · 2026-07-08 21:22:29 UTC
Parallelism
71/100
Blocked
30%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,487,821 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x744e0a36…70f7
0x34b655…2a6f
4 touches
1 conflict
0xbabbc95e…c450
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xfc366eef…6209
0x34b655…2a6f
3 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x1fab1722…aec5
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity