← previous blocknext block →recent activity

Analyzing

Block #74,392,347

30 transactions · 16 stateful · 2026-05-13 20:27:40 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,392,347  ·  30 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

0x3e473f6e…2157

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x580c6fe7…0fe4

0x1b6862…e19c

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x6d410e34…5e11

0x188d58…ea8e

2 touches
0 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: 0xd32edf66…9fff58

36 conflicts on slot 0x3e473f6ea1…ee2157

← previous block·next block →recent activity