← previous blocknext block →recent activity

Analyzing

Block #86,193,386

24 transactions · 18 stateful · 2026-07-07 12:35:28 UTC

Parallelism

88/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,193,386  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xdec5bfea…d17f

0xa6afd3…d132

6 touches
3 conflicts

0x202c03eb…cf33

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xfc77caf8…46cc

0xa6afd3…d132

4 touches
1 conflict

0x11560115…bfc2

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x3b8d7efd…a779

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity