← previous blocknext block →recent activity

Analyzing

Block #74,487,208

9 transactions · 8 stateful · 2026-05-14 06:59:06 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,487,208  ·  9 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

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xbaeed020…92f8

0x34b655…2a6f

2 touches
0 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

2 touches
0 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…1542

0x34b655…2a6f

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

1 conflict on slot 0x5aed1bd252…0a7afa

← previous block·next block →recent activity