← previous blocknext block →recent activity
Analyzing
Block #86,452,548
20 transactions · 20 stateful · 2026-07-08 17:26:29 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,452,548 · 20 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
1w02w13w24w16w07w08w110w111w213w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f34fd08…aeb3
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0xe1d1f14d…3ffb
0x34b655…2a6f
6 touches
3 conflicts
0x52c4533e…a648
0xd32edf…ff58
5 touches
3 conflicts
0x250c8181…eef2
0x34b655…2a6f
4 touches
1 conflict
0x2676caa7…8753
0x34b655…2a6f
4 touches
1 conflict
0x3592ddbc…334f
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x5f34fd08e4…a5aeb3
Audit this contract →
← previous block·next block →recent activity