← previous blocknext block →recent activity

Analyzing

Block #74,336,162

17 transactions · 10 stateful · 2026-05-13 14:13:52 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,336,162  ·  17 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

0x306f08ff…6e91

0x065c9d…c394

3 touches
1 conflict

0x0e467376…05b6

0x065c9d…c394

3 touches
1 conflict

0xa976d19d…543c

0x065c9d…c394

3 touches
1 conflict

0x45fb1e48…d0a5

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x82caa1b4…99a2

0x065c9d…c394

2 touches
0 conflicts

0x95a68198…c8aa

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