← previous blocknext block →recent activity

Analyzing

Block #89,579,470

20 transactions · 18 stateful · 2026-07-23 05:59:00 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,579,470  ·  20 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…0005

0x370e2e…63b4

14 touches
21 conflicts

0xbc0c65c4…7ece

0x0a2fbf…29b1

14 touches
21 conflicts

0xeac0c96e…b7fb

0x0a2fbf…29b1

14 touches
21 conflicts

0xeac0c96e…b7fc

0x0a2fbf…29b1

14 touches
21 conflicts

0xeac0c96e…b7ff

0x0a2fbf…29b1

14 touches
21 conflicts

0x00000000…0006

0x0a2fbf…29b1

14 touches
21 conflicts

0xbc0c65c4…7ecd

0x0a2fbf…29b1

14 touches
21 conflicts

0x1bff683e…7ecb

0x754704…b603

14 touches
21 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: 0x370e2ee6…bd63b4

21 conflicts on slot 0x0000000000…000005

← previous block·next block →recent activity