← previous blocknext block →recent activity

Analyzing

Block #74,918,632

31 transactions · 21 stateful · 2026-05-16 07:03:37 UTC

Parallelism

61/100

Blocked

62%

Avg conflicts / tx

2.23

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,918,632  ·  31 txs across 12 waves  ·  depth 12
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

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

0x1e5f3865…7814

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x1f8a126c…9aa6

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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

66 conflicts on slot 0x1e5f3865ea…237814

← previous block·next block →recent activity