← previous blocknext block →recent activity

Analyzing

Block #85,759,143

13 transactions · 8 stateful · 2026-07-05 12:19:11 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,759,143  ·  13 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x806b072c…4e98

0x34b655…2a6f

6 touches
3 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0x897a13fc…0f8a

0x34b655…2a6f

4 touches
1 conflict

0xb3c96942…f0fc

0x34b655…2a6f

4 touches
1 conflict

0x170e4e4c…2b90

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

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

3 conflicts on slot 0x806b072c54…894e98

← previous block·next block →recent activity