← previous blocknext block →recent activity

Analyzing

Block #74,183,708

16 transactions · 13 stateful · 2026-05-12 21:20:02 UTC

Parallelism

69/100

Blocked

46%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,183,708  ·  16 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

0x9748d2ca…cc11

0xd32edf…ff58

9 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x06e0e4cd…ce13

0x065c9d…c394

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0004

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x12530975…a089

0x3bd359…433a

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

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: 0xd32edf66…9fff58

10 conflicts on slot 0x9748d2ca9d…e9cc11

← previous block·next block →recent activity