← previous blocknext block →recent activity

Analyzing

Block #74,355,450

26 transactions · 19 stateful · 2026-05-13 16:22:07 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.04

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,355,450  ·  26 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x20ac0567…c954

0x34b655…2a6f

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x33a9b94b…286e

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity