← previous blocknext block →recent activity

Analyzing

Block #74,308,632

10 transactions · 8 stateful · 2026-05-13 11:10:49 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,308,632  ·  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

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x338a5e4f…2c4a

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xe6ff7b92…788b

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

4 touches
1 conflict

0xb3138aaf…edb3

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xbb1747e217…82f78b

← previous block·next block →recent activity