← previous blocknext block →recent activity

Analyzing

Block #74,196,999

15 transactions · 13 stateful · 2026-05-12 22:48:29 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,196,999  ·  15 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

0xcc4a72fb…372a

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0xc2da8b7b…4428

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x16740d4b…b75f

0xd32edf…ff58

3 touches
1 conflict

0x4396019f…a951

0x065c9d…c394

3 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

3 conflicts on slot 0xcc4a72fbf4…9e372a

← previous block·next block →recent activity