← previous blocknext block →recent activity

Analyzing

Block #74,774,733

5 transactions · 5 stateful · 2026-05-15 15:03:45 UTC

Parallelism

20/100

Blocked

60%

Avg conflicts / tx

1.2

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,774,733  ·  5 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

8 touches
6 conflicts

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x066998d2…b0e9

0x065c9d…c394

4 touches
1 conflict

0xb802c245…d5a6

0x065c9d…c394

2 touches
0 conflicts

0xdd232bae…577c

0x065c9d…c394

2 touches
0 conflicts

0xf3d7a307…4d63

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001a

0x1b6862…e19c

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity