← previous blocknext block →recent activity

Analyzing

Block #74,647,182

22 transactions · 21 stateful · 2026-05-15 00:51:50 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,647,182  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf98e221c…ffe8

0x34b655…2a6f

10 touches
10 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

6 touches
3 conflicts

0x01737532…9b12

0x34b655…2a6f

6 touches
3 conflicts

0x97d5efed…1aa4

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