← previous blocknext block →recent activity

Analyzing

Block #74,944,864

35 transactions · 27 stateful · 2026-05-16 09:58:52 UTC

Parallelism

57/100

Blocked

56%

Avg conflicts / tx

3.03

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,944,864  ·  35 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0xa472d565…9fe4

0x3bd359…433a

30 touches
105 conflicts

0xa10c86f8…4b74

0x3bd359…433a

20 touches
45 conflicts

0x00000000…0000

0x019883…2a9a

20 touches
45 conflicts

0x00000000…0002

0x019883…2a9a

20 touches
45 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

20 touches
45 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

20 touches
45 conflicts

0x73131ffc…b46c

0x5df178…7777

10 touches
10 conflicts

0x00000000…0001

0x2c492d…444e

10 touches
10 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: 0x3bd359c1…15433a

105 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity