← previous blocknext block →recent activity

Analyzing

Block #74,295,548

13 transactions · 11 stateful · 2026-05-13 09:43:44 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,295,548  ·  13 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xd6a59a38…0e08

0x065c9d…c394

3 touches
1 conflict

0x78ae17f2…53be

0x000000…012a

2 touches
0 conflicts

0x00000000…0001

0x010592…1c83

2 touches
0 conflicts

0x00000000…0006

0x010592…1c83

2 touches
0 conflicts

0x21abf21f…b7f5

0x010592…1c83

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