← previous blocknext block →recent activity

Analyzing

Block #74,240,840

20 transactions · 16 stateful · 2026-05-13 03:39:55 UTC

Parallelism

70/100

Blocked

63%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,240,840  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x010d2113…5905

0xd32edf…ff58

9 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x075d2ab6…44c1

0x34b655…2a6f

4 touches
1 conflict

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

10 conflicts on slot 0x010d2113a7…945905

← previous block·next block →recent activity