← previous blocknext block →recent activity

Analyzing

Block #74,456,878

24 transactions · 11 stateful · 2026-05-14 03:37:20 UTC

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,456,878  ·  24 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

0x51db12e4…feb6

0xd32edf…ff58

13 touches
21 conflicts

0x6aa624fd…a84f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x37b81d…17d7

4 touches
1 conflict

0x00000000…0002

0x37b81d…17d7

4 touches
1 conflict

0x00000000…0003

0x37b81d…17d7

4 touches
1 conflict

0x3b23d356…dcda

0x3bd359…433a

4 touches
1 conflict

0x551f6273…7c20

0x42a4aa…7777

4 touches
1 conflict

0xd06cc746…27e4

0x42a4aa…7777

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

21 conflicts on slot 0x51db12e4ba…dbfeb6

← previous block·next block →recent activity