← previous blocknext block →recent activity

Analyzing

Block #74,490,790

14 transactions · 13 stateful · 2026-05-14 07:22:56 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,490,790  ·  14 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

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x60dc69cc…0d19

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x622df421…3ad6

0x34b655…2a6f

4 touches
1 conflict

0x694b052d…3904

0x34b655…2a6f

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xab2ed10a…0265

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 0xf3981be56e…f02c47

← previous block·next block →recent activity