← previous blocknext block →recent activity

Analyzing

Block #74,010,250

11 transactions · 10 stateful · 2026-05-12 02:06:21 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,010,250  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0375b9c4…455d

0x2ab50b…5c41

2 touches
0 conflicts

0x0730e375…a5e0

0x2ab50b…5c41

2 touches
0 conflicts

0x0849cefc…6a65

0x2ab50b…5c41

2 touches
0 conflicts

0x15a8b5e6…0296

0x2ab50b…5c41

2 touches
0 conflicts

0x1bc4a8c0…7ea2

0x2ab50b…5c41

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity