← previous blocknext block →recent activity

Analyzing

Block #74,196,982

8 transactions · 6 stateful · 2026-05-12 22:48:22 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,196,982  ·  8 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

0xdd4fc8b9…04ff

0x065c9d…c394

4 touches
1 conflict

0x779e129d…698b

0x065c9d…c394

3 touches
1 conflict

0x914d1a18…d526

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0b6b8b2f…29e5

0x065c9d…c394

2 touches
0 conflicts

0x82dc6c89…552d

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

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 0xdd4fc8b9be…a004ff

← previous block·next block →recent activity