← previous blocknext block →recent activity

Analyzing

Block #74,781,799

20 transactions · 14 stateful · 2026-05-15 15:50:54 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,781,799  ·  20 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

8 touches
6 conflicts

0xff5c097d…680c

0x34b655…2a6f

6 touches
3 conflicts

0x15ea43ed…60a8

0xd32edf…ff58

5 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity