← previous blocknext block →recent activity

Analyzing

Block #74,331,246

22 transactions · 17 stateful · 2026-05-13 13:41:12 UTC

Parallelism

59/100

Blocked

59%

Avg conflicts / tx

1.14

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,331,246  ·  22 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

8 touches
6 conflicts

0x4381471a…9ac1

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x6d4a039a…06fd

0x34b655…2a6f

6 touches
3 conflicts

0x6fdaec06…a31f

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity