← previous blocknext block →recent activity

Analyzing

Block #74,649,068

19 transactions · 14 stateful · 2026-05-15 01:04:20 UTC

Parallelism

89/100

Blocked

21%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,649,068  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x91beca4c…a94b

0x065c9d…c394

4 touches
1 conflict

0x1378f5bb…283e

0xd32edf…ff58

3 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x558f6d0c…d50f

0x3bd359…433a

2 touches
0 conflicts

0xea9082f4…04a2

0x3bd359…433a

2 touches
0 conflicts

0x17606ba6…1b6e

0x754704…b603

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: 0x754704bc…afb603

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity