← previous blocknext block →recent activity

Analyzing

Block #74,353,771

29 transactions · 13 stateful · 2026-05-13 16:10:55 UTC

Parallelism

90/100

Blocked

23%

Avg conflicts / tx

0.1

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,353,771  ·  29 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0x95eabf72…43f1

0x34b655…2a6f

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x815e5dcc…819a

0x065c9d…c394

2 touches
0 conflicts

0xb8d901f5…e0ed

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity