← previous blocknext block →recent activity

Analyzing

Block #74,920,215

40 transactions · 28 stateful · 2026-05-16 07:14:12 UTC

Parallelism

77/100

Blocked

68%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,920,215  ·  40 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

0xba38536d…2b7d

0x065c9d…c394

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 conflicts

0x74e94e75…4913

0x34b655…2a6f

8 touches
6 conflicts

0x9256b810…52cc

0x1b6862…e19c

8 touches
6 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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity