← previous blocknext block →recent activity

Analyzing

Block #74,423,196

22 transactions · 14 stateful · 2026-05-13 23:53:00 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,423,196  ·  22 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

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xce1f0d41…2ab1

0xd32edf…ff58

5 touches
3 conflicts

0xab621973…cc16

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x5a3732cb…edaf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0xadac4a860c…a3c2bc

← previous block·next block →recent activity