← previous blocknext block →recent activity

Analyzing

Block #74,423,117

36 transactions · 31 stateful · 2026-05-13 23:52:29 UTC

Parallelism

78/100

Blocked

55%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,423,117  ·  36 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x4407eb6b…561f

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xd7a175ca…f443

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

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

21 conflicts on slot 0x4407eb6b3a…99561f

← previous block·next block →recent activity