← previous blocknext block →recent activity

Analyzing

Block #74,241,015

12 transactions · 8 stateful · 2026-05-13 03:41:05 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,241,015  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x15cb5c8d…8f25

0x065c9d…c394

2 touches
0 conflicts

0x311ea9f6…200f

0x065c9d…c394

2 touches
0 conflicts

0xb25dd395…fbed

0x065c9d…c394

2 touches
0 conflicts

0xdf2e7f2c…e329

0x065c9d…c394

2 touches
0 conflicts

0xe2d66c5f…a39f

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity