← previous blocknext block →recent activity

Analyzing

Block #74,484,547

35 transactions · 23 stateful · 2026-05-14 06:41:23 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.4

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,484,547  ·  35 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

0x93ed92e7…76e3

0xd32edf…ff58

19 touches
45 conflicts

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

2 touches
0 conflicts

0x4e368b2b…09ac

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

45 conflicts on slot 0x93ed92e7f6…f776e3

← previous block·next block →recent activity