← previous blocknext block →recent activity

Analyzing

Block #74,197,110

13 transactions · 13 stateful · 2026-05-12 22:49:12 UTC

Parallelism

62/100

Blocked

62%

Avg conflicts / tx

1.31

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,197,110  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x60b8fb2a…61c2

0x34b655…2a6f

4 touches
1 conflict

0xcc4a72fb…372a

0x065c9d…c394

4 touches
1 conflict

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

10 conflicts on slot 0xf823e97fa0…262ee6

← previous block·next block →recent activity