← previous blocknext block →recent activity

Analyzing

Block #74,644,015

18 transactions · 14 stateful · 2026-05-15 00:30:45 UTC

Parallelism

56/100

Blocked

57%

Avg conflicts / tx

1.61

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,644,015  ·  18 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

0x4acdf4e5…5976

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x73912233…4589

0x1b6862…e19c

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x019883…2a9a

4 touches
1 conflict

0x00000000…0002

0x019883…2a9a

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

28 conflicts on slot 0x4acdf4e585…e25976

← previous block·next block →recent activity