← previous blocknext block →recent activity

Analyzing

Block #74,402,424

15 transactions · 12 stateful · 2026-05-13 21:34:49 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,402,424  ·  15 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

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x76e559a4…77fb

0x2a68ba…90c5

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x4949f7b9…2505

0x065c9d…c394

2 touches
0 conflicts

0x962a2ed5…e4fb

0x065c9d…c394

2 touches
0 conflicts

0xef31ee52…dbbe

0x065c9d…c394

2 touches
0 conflicts

0x194f2c02…19e6

0x2a68ba…90c5

2 touches
0 conflicts

0x92d610a6…9a40

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity