← previous blocknext block →recent activity

Analyzing

Block #74,359,796

13 transactions · 8 stateful · 2026-05-13 16:51:00 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,359,796  ·  13 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

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x18e45ee7…cdfd

0x065c9d…c394

2 touches
0 conflicts

0x1f9be478…e25e

0x065c9d…c394

2 touches
0 conflicts

0x54535367…9e97

0x065c9d…c394

2 touches
0 conflicts

0xa54e967f…7e3a

0x065c9d…c394

2 touches
0 conflicts

0xd33485b0…3f5a

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: 0x065c9d28…a9c394

1 conflict on slot 0x47b807a243…c53307

← previous block·next block →recent activity