← previous blocknext block →recent activity

Analyzing

Block #74,188,246

12 transactions · 10 stateful · 2026-05-12 21:50:09 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,188,246  ·  12 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x21adc8b6…3fa7

0x065c9d…c394

2 touches
0 conflicts

0x5da7d26f…e59e

0x065c9d…c394

2 touches
0 conflicts

0xad57c913…70cf

0x065c9d…c394

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity