← previous blocknext block →recent activity

Analyzing

Block #74,787,820

24 transactions · 15 stateful · 2026-05-15 16:31:12 UTC

Parallelism

88/100

Blocked

47%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,787,820  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x9c98462b…9f83

0xd32edf…ff58

5 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x4002395e…ae61

0x34b655…2a6f

4 touches
1 conflict

0x5ffc25fa…b119

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity