← previous blocknext block →recent activity

Analyzing

Block #74,316,491

37 transactions · 25 stateful · 2026-05-13 12:03:03 UTC

Parallelism

81/100

Blocked

56%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,316,491  ·  37 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

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0xe4889b6a…fd02

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0029

0x1b6862…e19c

6 touches
3 conflicts

0x115f766b…47d2

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

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: 0x754704bc…afb603

10 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity