← previous blocknext block →recent activity

Analyzing

Block #74,241,559

29 transactions · 23 stateful · 2026-05-13 03:44:43 UTC

Parallelism

79/100

Blocked

43%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,241,559  ·  29 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

0xe97f2fe2…ca4b

0xd32edf…ff58

11 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x41335ddf…94b9

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xce8bbe33…b72e

0x3bd359…433a

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

15 conflicts on slot 0xe97f2fe2f6…4eca4b

← previous block·next block →recent activity