← previous blocknext block →recent activity

Analyzing

Block #74,427,283

20 transactions · 15 stateful · 2026-05-14 00:20:16 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,427,283  ·  20 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xe70c0780…6876

0xd32edf…ff58

3 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0000

0x63e48b…53f2

2 touches
0 conflicts

0x00000000…0003

0x63e48b…53f2

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity