← previous blocknext block →recent activity

Analyzing

Block #74,216,452

8 transactions · 6 stateful · 2026-05-13 00:57:47 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,216,452  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x75f928fc…0465

0x34b655…2a6f

4 touches
1 conflict

0xba3f84a5…4c26

0x34b655…2a6f

4 touches
1 conflict

0x1c4a904f…36fa

0x065c9d…c394

2 touches
0 conflicts

0x27483636…c2cf

0x065c9d…c394

2 touches
0 conflicts

0x34e2ee3c…fdda

0x065c9d…c394

2 touches
0 conflicts

0x470e6172…9c2a

0x065c9d…c394

2 touches
0 conflicts

0xc0e8c6e8…f5b8

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

← previous block·next block →recent activity