← previous blocknext block →recent activity

Analyzing

Block #74,686,733

28 transactions · 18 stateful · 2026-05-15 05:15:42 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1.21

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,686,733  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x28e637e1…d832

0xd32edf…ff58

15 touches
28 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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: 0xd32edf66…9fff58

28 conflicts on slot 0x28e637e16f…56d832

← previous block·next block →recent activity