← previous blocknext block →recent activity

Analyzing

Block #74,479,239

9 transactions · 8 stateful · 2026-05-14 06:06:03 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,479,239  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xac92a59c…0a72

0x699abc…6a3b

4 touches
1 conflict

0xe1aa2d73…861e

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2f1b25f6…7c15

0x34b655…2a6f

2 touches
0 conflicts

0x4118bd12…924a

0x34b655…2a6f

2 touches
0 conflicts

0x742436a7…c4d4

0x34b655…2a6f

2 touches
0 conflicts

0x2e03c1b7…b307

0x754704…b603

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: 0x699abc15…c86a3b

1 conflict on slot 0xac92a59c7e…310a72

← previous block·next block →recent activity