← previous blocknext block →recent activity

Analyzing

Block #74,761,172

48 transactions · 29 stateful · 2026-05-15 13:32:52 UTC

Parallelism

81/100

Blocked

55%

Avg conflicts / tx

1.04

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,761,172  ·  48 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7a79b753…00d2

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x580c6fe7…0fe4

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

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

36 conflicts on slot 0x7a79b75356…6c00d2

← previous block·next block →recent activity