← previous blocknext block →recent activity
Analyzing
Block #86,855,279
13 transactions · 11 stateful · 2026-07-10 14:20:20 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,855,279 · 13 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
2w03w16w27w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x17a61764…186d
0x34b655…2a6f
4 touches
1 conflict
0x2b9ff7c3…a477
0x34b655…2a6f
4 touches
1 conflict
0x2b9ff7c3…a478
0x34b655…2a6f
4 touches
1 conflict
0x3c018cfe…5403
0x34b655…2a6f
4 touches
1 conflict
0xe451607f…5822
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7e
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity