← previous blocknext block →recent activity

Analyzing

Block #74,334,223

39 transactions · 24 stateful · 2026-05-13 14:00:59 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,334,223  ·  39 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

0x23797383…99de

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x8256a78f…5a0b

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x11998eac…f9a0

0x1b6862…e19c

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

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 0x23797383d3…a999de

← previous block·next block →recent activity