← previous blocknext block →recent activity

Analyzing

Block #74,359,777

16 transactions · 9 stateful · 2026-05-13 16:50:53 UTC

Parallelism

81/100

Blocked

22%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,359,777  ·  16 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

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x976f577b…3916

0x065c9d…c394

2 touches
0 conflicts

0xd039c8fc…3f05

0x065c9d…c394

2 touches
0 conflicts

0x9c4a4b0d…abdd

0x1001ff…1001

2 touches
0 conflicts

0xc6f1b3af…c97c

0x1001ff…1001

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