← previous blocknext block →recent activity

Analyzing

Block #74,484,713

27 transactions · 13 stateful · 2026-05-14 06:42:29 UTC

Parallelism

89/100

Blocked

23%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,484,713  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbc04d98e…a484

0x34b655…2a6f

4 touches
1 conflict

0x543da691…8f99

0x34b655…2a6f

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity