← previous blocknext block →recent activity

Analyzing

Block #74,346,825

17 transactions · 12 stateful · 2026-05-13 15:24:47 UTC

Parallelism

82/100

Blocked

17%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,825  ·  17 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x6fce7a05…d778

0x34b655…2a6f

4 touches
1 conflict

0x76eb9e75…d982

0x34b655…2a6f

4 touches
1 conflict

0x898a1a2f…bf47

0x34b655…2a6f

4 touches
1 conflict

0xb5153247…dd9c

0x34b655…2a6f

4 touches
1 conflict

0xc16e646d…4fb0

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity