← previous blocknext block →recent activity

Analyzing

Block #88,083,912

18 transactions · 17 stateful · 2026-07-16 07:17:10 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,083,912  ·  18 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

0x00000000…0006

0x0a2fbf…29b1

8 touches
6 conflicts

0x4c1dc38d…4875

0x0a2fbf…29b1

8 touches
6 conflicts

0x4c1dc38d…4876

0x0a2fbf…29b1

8 touches
6 conflicts

0x4c1dc38d…4879

0x0a2fbf…29b1

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x55b4e430…44cb

0x754704…b603

8 touches
6 conflicts

0xbd6e61f7…3ede

0x34b655…2a6f

6 touches
3 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: 0x0a2fbf2d…f729b1

6 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity