← previous blocknext block →recent activity

Analyzing

Block #74,771,725

24 transactions · 10 stateful · 2026-05-15 14:43:37 UTC

Parallelism

88/100

Blocked

20%

Avg conflicts / tx

0.08

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,771,725  ·  24 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

0x0a2250a8…3cb1

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x37f1c051…ff6b

0x065c9d…c394

2 touches
0 conflicts

0x40cd32ac…ca7f

0x065c9d…c394

2 touches
0 conflicts

0x7ec97208…bc91

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 0x0a2250a863…a83cb1

← previous block·next block →recent activity