← previous blocknext block →recent activity

Analyzing

Block #85,350,963

21 transactions · 21 stateful · 2026-07-03 15:00:04 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,350,963  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf79df061…e005

0xe52b14…7230

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x7e10454f…4d9e

0xa6afd3…d132

4 touches
1 conflict

0x8a751d7a…247c

0xa6afd3…d132

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x40970e69…da50

0x69df8a…6292

2 touches
0 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: 0xe52b1424…bb7230

6 conflicts on slot 0xf79df061c7…91e005

← previous block·next block →recent activity