← previous blocknext block →recent activity

Analyzing

Block #74,260,531

16 transactions · 10 stateful · 2026-05-13 05:50:45 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,260,531  ·  16 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xae93f44d…a64c

0x065c9d…c394

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xdd12bf3f…de62

0xd32edf…ff58

3 touches
1 conflict

0xd36d78c5…75f3

0x065c9d…c394

3 touches
1 conflict

0x7ad7e0c1…946c

0x065c9d…c394

2 touches
0 conflicts

0x89ab8183…9a76

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity