← previous blocknext block →recent activity

Analyzing

Block #85,615,101

20 transactions · 20 stateful · 2026-07-04 20:18:52 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,615,101  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0x7fa44fe8…484e

0x34b655…2a6f

4 touches
1 conflict

0x9985dbdd…c2a3

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity