← previous blocknext block →recent activity

Analyzing

Block #85,919,212

29 transactions · 24 stateful · 2026-07-06 06:05:19 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,919,212  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0x04fdea…47d7

14 touches
21 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb4c35fcd…43ae

0xa6afd3…d132

6 touches
3 conflicts

0x2f047f1d…60fa

0xa6afd3…d132

4 touches
2 conflicts

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

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: 0x04fdeac2…f747d7

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity