← previous blocknext block →recent activity

Analyzing

Block #74,632,405

16 transactions · 12 stateful · 2026-05-14 23:13:21 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,632,405  ·  16 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

0x5cdb49eb…617e

0xd32edf…ff58

11 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x17ca7036…1e1b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002f

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0xd32edf66…9fff58

15 conflicts on slot 0x5cdb49eb75…36617e

← previous block·next block →recent activity