← previous blocknext block →recent activity

Analyzing

Block #74,223,603

10 transactions · 10 stateful · 2026-05-13 01:45:22 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,223,603  ·  10 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

0x1b159f3d…9163

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x31684ff4…a2a6

0x065c9d…c394

2 touches
0 conflicts

0x5c2f2bb1…2bd9

0x065c9d…c394

2 touches
0 conflicts

0x7a507a12…4801

0x065c9d…c394

2 touches
0 conflicts

0x83fed057…fd9c

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: 0x34b6552d…112a6f

1 conflict on slot 0x1b159f3da1…2a9163

← previous block·next block →recent activity