← previous blocknext block →recent activity

Analyzing

Block #74,248,551

10 transactions · 10 stateful · 2026-05-13 04:31:14 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,248,551  ·  10 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x911772c2…03ae

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xa51ca39b…7b7b

0x065c9d…c394

3 touches
1 conflict

0x2c14e3fe…83f7

0x065c9d…c394

3 touches
1 conflict

0xc0d9647b…3afa

0x065c9d…c394

3 touches
1 conflict

0x718f5fc1…b83c

0x065c9d…c394

2 touches
0 conflicts

0xac1ad7e5…b490

0x065c9d…c394

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity