← previous blocknext block →recent activity

Analyzing

Block #74,247,546

10 transactions · 9 stateful · 2026-05-13 04:24:31 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,247,546  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x515d39f1…ea6d

0x065c9d…c394

2 touches
0 conflicts

0x64ed3e6e…d5b0

0x065c9d…c394

2 touches
0 conflicts

0x84da660a…5a39

0x065c9d…c394

2 touches
0 conflicts

0xc89e01c9…91a4

0x065c9d…c394

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 0xf2f76ab392…f3623e

← previous block·next block →recent activity