← previous blocknext block →recent activity

Analyzing

Block #74,041,530

29 transactions · 19 stateful · 2026-05-12 05:33:59 UTC

Parallelism

66/100

Blocked

58%

Avg conflicts / tx

1.62

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,041,530  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x052a8a5b…bc3d

0xd32edf…ff58

19 touches
45 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xcb45d9d6…cb83

0x1b6862…e19c

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

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

45 conflicts on slot 0x052a8a5b7e…ffbc3d

← previous block·next block →recent activity