← previous blocknext block →recent activity

Analyzing

Block #74,390,209

11 transactions · 8 stateful · 2026-05-13 20:13:27 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,390,209  ·  11 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xc08384da…ecb7

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

2 touches
0 conflicts

0x72a152dd…9fa1

0x16f70c…c3dd

2 touches
0 conflicts

0x3dea5c3d…5fb8

0x58e158…3d57

2 touches
0 conflicts

0x4eb17750…19cd

0x58e158…3d57

2 touches
0 conflicts

0x524ab099…0cd8

0x58e158…3d57

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity