← previous blocknext block →recent activity
Analyzing
Block #86,768,624
14 transactions · 10 stateful · 2026-07-10 04:41:14 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,768,624 · 14 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x236b16bf…ea47
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0e403c18…eac8
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015a
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015b
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x3a2a8323…3f40
0x34b655…2a6f
2 touches
0 conflicts
0x5dc93134…aaef
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 0x236b16bfa6…6dea47
Audit this contract →
← previous block·next block →recent activity