← previous blocknext block →recent activity

Analyzing

Block #74,204,599

16 transactions · 14 stateful · 2026-05-12 23:38:57 UTC

Parallelism

63/100

Blocked

64%

Avg conflicts / tx

1.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,204,599  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

6 touches
3 conflicts

0x7084519d…e0a1

0x34b655…2a6f

4 touches
1 conflict

0x71e4ffd1…9beb

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity