← previous blocknext block →recent activity

Analyzing

Block #74,382,820

13 transactions · 12 stateful · 2026-05-13 19:24:16 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,382,820  ·  13 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x76aea06d…40ae

0xd32edf…ff58

5 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x95fb069d…3de7

0x065c9d…c394

3 touches
1 conflict

0x50e40524…51a0

0x065c9d…c394

3 touches
1 conflict

0x014e90b3…470f

0x34b655…2a6f

3 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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity