← previous blocknext block →recent activity
Analyzing
Block #86,965,171
14 transactions · 12 stateful · 2026-07-11 02:34:56 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,965,171 · 14 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
2w07w18w29w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb66ad8f…5f38
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x226e3b61…5e6f
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
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
1 conflict on slot 0xeb66ad8fb7…015f38
Audit this contract →
← previous block·next block →recent activity