← previous blocknext block →recent activity

Analyzing

Block #74,509,027

24 transactions · 18 stateful · 2026-05-14 09:24:55 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,509,027  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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