← previous blocknext block →recent activity

Analyzing

Block #74,248,385

17 transactions · 13 stateful · 2026-05-13 04:30:07 UTC

Parallelism

76/100

Blocked

46%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,248,385  ·  17 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

0x38b47976…4f49

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x3c81fa55…58e1

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0x094452…0a09

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

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

3 conflicts on slot 0x38b4797624…744f49

← previous block·next block →recent activity