← previous blocknext block →recent activity

Analyzing

Block #74,762,869

16 transactions · 8 stateful · 2026-05-15 13:44:16 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,762,869  ·  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

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x5929bce3…ea01

0x34b655…2a6f

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0f028d67…1608

0x065c9d…c394

2 touches
0 conflicts

0x23f9bc7e…140b

0x065c9d…c394

2 touches
0 conflicts

0x5886663c…6c87

0x065c9d…c394

2 touches
0 conflicts

0x7ed4d53e…de8d

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 0x41d3bfa533…31523e

← previous block·next block →recent activity