← previous blocknext block →recent activity

Analyzing

Block #74,196,841

12 transactions · 9 stateful · 2026-05-12 22:47:25 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,196,841  ·  12 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x9917652d…89a8

0xd32edf…ff58

3 touches
1 conflict

0x2cdce0d2…f2e3

0x065c9d…c394

2 touches
0 conflicts

0x5fe2432e…53c2

0x065c9d…c394

2 touches
0 conflicts

0x937866f9…04b6

0x065c9d…c394

2 touches
0 conflicts

0x9e7ae34c…de94

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 0x0000000000…00003d

← previous block·next block →recent activity