← previous blocknext block →recent activity

Analyzing

Block #74,040,345

25 transactions · 21 stateful · 2026-05-12 05:26:07 UTC

Parallelism

64/100

Blocked

62%

Avg conflicts / tx

1.8

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,040,345  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xdaca243a…f9de

0x34b655…2a6f

18 touches
36 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc7f28b7a…5777

0x34b655…2a6f

8 touches
6 conflicts

0x070a562a…8147

0x34b655…2a6f

7 touches
6 conflicts

0xce119dd7…26cf

0xd32edf…ff58

7 touches
6 conflicts

0x758ac670…3ec6

0x34b655…2a6f

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

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: 0x34b6552d…112a6f

36 conflicts on slot 0xdaca243a5e…09f9de

← previous block·next block →recent activity