← previous blocknext block →recent activity
Analyzing
Block #86,820,237
10 transactions · 9 stateful · 2026-07-10 10:25:57 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,820,237 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf898a83a…3f62
0x34b655…2a6f
4 touches
1 conflict
0x16363afe…d410
0x34b655…2a6f
4 touches
1 conflict
0x1b504486…913b
0x34b655…2a6f
4 touches
1 conflict
0xa5864fb7…c41f
0x34b655…2a6f
4 touches
1 conflict
0xc6a72539…9ecb
0x34b655…2a6f
4 touches
1 conflict
0xd7789c26…9e61
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x43121a72…4b1c
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 0xf898a83a27…a13f62
Audit this contract →
← previous block·next block →recent activity