← previous blocknext block →recent activity
Analyzing
Block #85,201,210
21 transactions · 18 stateful · 2026-07-02 22:22:30 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,201,210 · 21 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
2w05w06w17w28w39w410w111w213w014w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x2917f81e…fce6
0x34b655…2a6f
8 touches
6 conflicts
0x3fde350e…8d43
0x34b655…2a6f
8 touches
6 conflicts
0x4eed0a91…acd1
0x34b655…2a6f
8 touches
6 conflicts
0x06aed19e…ca57
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity