← previous blocknext block →recent activity

Analyzing

Block #74,040,826

8 transactions · 7 stateful · 2026-05-12 05:29:18 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,826  ·  8 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0001

0x5c533c…a5a6

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x8fe00e6e…c0f1

0x065c9d…c394

3 touches
1 conflict

0x4c9f6b9a…e1a7

0x065c9d…c394

3 touches
1 conflict

0x595c0486…e370

0x065c9d…c394

2 touches
0 conflicts

0x92c60916…fe4d

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity