← previous blocknext block →recent activity

Analyzing

Block #74,425,629

12 transactions · 11 stateful · 2026-05-14 00:09:15 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,425,629  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x1279ee2d…ae99

0x34b655…2a6f

4 touches
1 conflict

0x157d1e46…85f6

0x34b655…2a6f

4 touches
1 conflict

0x764f2d09…bc43

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xd40bddc1…773c

0x34b655…2a6f

4 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 0xbad6855239…f0e6bf

← previous block·next block →recent activity