← previous blocknext block →recent activity

Analyzing

Block #86,301,927

21 transactions · 19 stateful · 2026-07-08 00:40:12 UTC

Parallelism

81/100

Blocked

42%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,301,927  ·  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

0xffa7d0a4…b10a

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x342fbbca…d443

0x40c49f…2af0

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xa19aba84…8922

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x46b62326…9b3c

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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: 0x40c49f17…d22af0

6 conflicts on slot 0xffa7d0a419…63b10a

← previous block·next block →recent activity