← previous blocknext block →recent activity

Analyzing

Block #74,355,032

13 transactions · 13 stateful · 2026-05-13 16:19:20 UTC

Parallelism

77/100

Blocked

15%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,355,032  ·  13 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

0xd40bddc1…773c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x8e594d49…0f8f

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x6e7b76ae…d3da

0x065c9d…c394

2 touches
0 conflicts

0x87881779…4523

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 0xd40bddc144…4e773c

← previous block·next block →recent activity