← previous blocknext block →recent activity

Analyzing

Block #74,255,241

11 transactions · 10 stateful · 2026-05-13 05:15:40 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,255,241  ·  11 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

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x6218cdb8…0852

0x34b655…2a6f

2 touches
0 conflicts

0xde8d683d…0d0f

0x34b655…2a6f

2 touches
0 conflicts

0xea6d137e…7285

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

3 conflicts on slot 0x7b7bcac3fe…968fbf

← previous block·next block →recent activity