← previous blocknext block →recent activity

Analyzing

Block #85,573,486

20 transactions · 16 stateful · 2026-07-04 15:41:43 UTC

Parallelism

70/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,573,486  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xc400ddde…e754

0x34b655…2a6f

6 touches
3 conflicts

0xd5aa8069…a135

0x34b655…2a6f

6 touches
3 conflicts

0x05edf2cf…ac3c

0x34b655…2a6f

5 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x7a2fc410…c088

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

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

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity