← previous blocknext block →recent activity

Analyzing

Block #74,453,223

19 transactions · 11 stateful · 2026-05-14 03:12:55 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.32

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,453,223  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0de7749d…5bef

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x39ccd26a…4654

0x34b655…2a6f

6 touches
3 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x2a95b768…2d9d

0x34b655…2a6f

4 touches
1 conflict

0x4d63bc0a…65d8

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity