← previous blocknext block →recent activity

Analyzing

Block #74,665,229

19 transactions · 16 stateful · 2026-05-15 02:52:24 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,665,229  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xd62f3741…b903

0x34b655…2a6f

8 touches
6 conflicts

0x07c47b1c…93c8

0x34b655…2a6f

8 touches
6 conflicts

0x04f0e47d…cb70

0x34b655…2a6f

6 touches
3 conflicts

0x6d4c8680…6062

0x34b655…2a6f

6 touches
3 conflicts

0x3ebaf0ea…87c4

0x34b655…2a6f

6 touches
3 conflicts

0x81e1f4e8…08d7

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: Perpl

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity