← previous blocknext block →recent activity

Analyzing

Block #74,182,649

26 transactions · 22 stateful · 2026-05-12 21:13:00 UTC

Parallelism

77/100

Blocked

59%

Avg conflicts / tx

1.04

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,182,649  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7ceefb86…9754

0xd32edf…ff58

9 touches
10 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

8 touches
6 conflicts

0xb1406cb1…95b1

0x34b655…2a6f

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xd77e90ec…8c04

0x3bd359…433a

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

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

10 conflicts on slot 0x7ceefb86f2…f39754

← previous block·next block →recent activity