← previous blocknext block →recent activity

Analyzing

Block #74,589,940

16 transactions · 9 stateful · 2026-05-14 18:29:31 UTC

Parallelism

88/100

Blocked

11%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,589,940  ·  16 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

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x38a06385…ed6a

0x34b655…2a6f

4 touches
1 conflict

0x84aef2aa…979f

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x8d781551…f38d

0x065c9d…c394

2 touches
0 conflicts

0xa4725660…6ee3

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 0xea02471df2…601542

← previous block·next block →recent activity