← previous blocknext block →recent activity

Analyzing

Block #74,637,901

39 transactions · 28 stateful · 2026-05-14 23:50:02 UTC

Parallelism

80/100

Blocked

64%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,637,901  ·  39 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

0x00000000…0002

0xab3526…fa38

16 touches
28 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf578f018…197c

0xd32edf…ff58

7 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x5d82c9b5…004c

0x3bd359…433a

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: 0xab35264b…1cfa38

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity