← previous blocknext block →recent activity

Analyzing

Block #74,344,894

18 transactions · 17 stateful · 2026-05-13 15:11:55 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,344,894  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x394c3833…b4a8

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x46126857…3872

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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: 0x1b68626d…2de19c

3 conflicts on slot 0x394c38330b…c9b4a8

← previous block·next block →recent activity