← previous blocknext block →recent activity

Analyzing

Block #74,284,520

9 transactions · 9 stateful · 2026-05-13 08:30:19 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,284,520  ·  9 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

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3e38d1a2…4b35

0x065c9d…c394

3 touches
1 conflict

0xae772ade…5ab0

0x065c9d…c394

3 touches
1 conflict

0x3bc2e97a…4077

0x065c9d…c394

2 touches
0 conflicts

0x51594bd6…fa03

0x065c9d…c394

2 touches
0 conflicts

0x78f0579f…e81a

0x065c9d…c394

2 touches
0 conflicts

0x96d40658…3892

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

1 conflict on slot 0xf823e97fa0…262ee6

← previous block·next block →recent activity