← previous blocknext block →recent activity

Analyzing

Block #74,654,440

17 transactions · 12 stateful · 2026-05-15 01:40:17 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,654,440  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e68541c…c4b2

0xd32edf…ff58

5 touches
3 conflicts

0x37674bd8…8f35

0x34b655…2a6f

4 touches
1 conflict

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002f

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c6

0x1b6862…e19c

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity