← previous blocknext block →recent activity

Analyzing

Block #74,595,770

15 transactions · 14 stateful · 2026-05-14 19:08:31 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,595,770  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbbee74c2…567a

0x065c9d…c394

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xfcbffb63…61b4

0x065c9d…c394

5 touches
3 conflicts

0xa36ce883…837d

0x065c9d…c394

4 touches
2 conflicts

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0xada193dc…5c7f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

10 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity