← previous blocknext block →recent activity

Analyzing

Block #74,224,857

15 transactions · 11 stateful · 2026-05-13 01:53:40 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,224,857  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x9288e471…c99b

0x34b655…2a6f

6 touches
3 conflicts

0x99a3a7c1…1e2b

0x0cc9b2…7777

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x71e96b74…abe9

0x34b655…2a6f

4 touches
1 conflict

0x8b8e4020…11b0

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

6 conflicts on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity