← previous blocknext block →recent activity

Analyzing

Block #85,540,784

20 transactions · 17 stateful · 2026-07-04 12:03:59 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,540,784  ·  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

8 touches
6 conflicts

0xcf827da3…f2a5

0x34b655…2a6f

6 touches
3 conflicts

0x7e4b5149…c444

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xafb2524a…0ce4

0x34b655…2a6f

6 touches
3 conflicts

0x33e3dcdd…1f1f

0x34b655…2a6f

4 touches
1 conflict

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x5fad6fee…7714

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity