← previous blocknext block →recent activity

Analyzing

Block #74,215,349

8 transactions · 7 stateful · 2026-05-13 00:50:25 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,215,349  ·  8 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

0xaf498679…7732

0x34b655…2a6f

4 touches
1 conflict

0xfbbc35e2…f66b

0x34b655…2a6f

4 touches
1 conflict

0x2b4e1915…8a3a

0x1efe02…37d6

2 touches
0 conflicts

0xb0059330…5947

0x1efe02…37d6

2 touches
0 conflicts

0x0e7d4ad9…3d73

0xea1b8e…c5ec

2 touches
0 conflicts

0x1728ed63…499c

0xea1b8e…c5ec

2 touches
0 conflicts

0x3f366c54…957b

0xea1b8e…c5ec

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity