← previous blocknext block →recent activity

Analyzing

Block #74,224,817

11 transactions · 10 stateful · 2026-05-13 01:53:24 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,224,817  ·  11 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…003d

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x3bd27345…d902

0x065c9d…c394

2 touches
0 conflicts

0x44a80a7e…27fe

0x065c9d…c394

2 touches
0 conflicts

0x63bf6666…a789

0x065c9d…c394

2 touches
0 conflicts

0x7da6a2f8…c56c

0x065c9d…c394

2 touches
0 conflicts

0x941e386f…3817

0x065c9d…c394

2 touches
0 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity