← previous blocknext block →recent activity

Analyzing

Block #74,234,247

32 transactions · 28 stateful · 2026-05-13 02:56:07 UTC

Parallelism

78/100

Blocked

61%

Avg conflicts / tx

1.44

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,234,247  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcf3283ba…c9fa

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 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: 0x065c9d28…a9c394

10 conflicts on slot 0xcf3283bab2…c3c9fa

← previous block·next block →recent activity