← previous blocknext block →recent activity

Analyzing

Block #74,216,308

4 transactions · 4 stateful · 2026-05-13 00:56:50 UTC

Parallelism

50/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,216,308  ·  4 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc166a323…1f33

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0xba3f84a5…4c26

0x34b655…2a6f

4 touches
1 conflict

0xfe20cb8f…f03d

0x34b655…2a6f

3 touches
1 conflict

0x2965e2d6…5800

0x34b655…2a6f

2 touches
0 conflicts

0x1fd20d14…80dd

0x34b655…2a6f

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

1 conflict on slot 0x75f928fcad…c20465

← previous block·next block →recent activity