← previous blocknext block →recent activity

Analyzing

Block #74,331,906

31 transactions · 17 stateful · 2026-05-13 13:45:33 UTC

Parallelism

87/100

Blocked

35%

Avg conflicts / tx

0.23

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,331,906  ·  31 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

0x9a291a56…9a9c

0x34b655…2a6f

4 touches
1 conflict

0x5ffc25fa…b119

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x81f76c8c…a0c7

0x065c9d…c394

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: Perpl

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity