← previous blocknext block →recent activity

Analyzing

Block #74,649,343

31 transactions · 21 stateful · 2026-05-15 01:06:10 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

0.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,649,343  ·  31 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x47b2d2eb…8aa5

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd8d828a7…b64f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x34b6552d…112a6f

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity