← previous blocknext block →recent activity

Analyzing

Block #74,215,556

22 transactions · 19 stateful · 2026-05-13 00:51:48 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1.27

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,215,556  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

6 touches
3 conflicts

0x79337440…499d

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity