← previous blocknext block →recent activity

Analyzing

Block #85,873,102

20 transactions · 14 stateful · 2026-07-06 00:58:08 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,873,102  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0672e4a2…8d1f

0x34b655…2a6f

8 touches
6 conflicts

0xbe9baf16…df37

0x34b655…2a6f

8 touches
6 conflicts

0x5fd52d9f…e3c6

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x3da7c2bd…1ede

0x34b655…2a6f

4 touches
1 conflict

0x48b13e5e…3c2a

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

6 conflicts on slot 0x0672e4a279…2f8d1f

← previous block·next block →recent activity