← previous blocknext block →recent activity

Analyzing

Block #74,240,648

10 transactions · 10 stateful · 2026-05-13 03:38:39 UTC

Parallelism

70/100

Blocked

30%

Avg conflicts / tx

0.7

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,240,648  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x68e47301…5df5

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xb98ddaa5…9bfb

0x065c9d…c394

4 touches
1 conflict

0x98e57069…8bb4

0x065c9d…c394

4 touches
1 conflict

0xec7ebd97…da7c

0x065c9d…c394

3 touches
1 conflict

0x8e8bc24a…67e8

0x065c9d…c394

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity