← previous blocknext block →recent activity

Analyzing

Block #74,736,268

18 transactions · 16 stateful · 2026-05-15 10:46:20 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,736,268  ·  18 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

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x04bda8e1…b3ae

0xd32edf…ff58

5 touches
3 conflicts

0x735592a7…84cb

0x065c9d…c394

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0x7f93f279…f82a

0x065c9d…c394

2 touches
0 conflicts

0x2f77f0f6…4a92

0x188d58…ea8e

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity