← previous blocknext block →recent activity

Analyzing

Block #74,630,893

13 transactions · 12 stateful · 2026-05-14 23:03:21 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,630,893  ·  13 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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0x3173f4cf…c312

0x065c9d…c394

2 touches
0 conflicts

0x31be930d…6cb0

0x065c9d…c394

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…00c9

0x34b655…2a6f

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity