← previous blocknext block →recent activity

Analyzing

Block #74,624,322

17 transactions · 10 stateful · 2026-05-14 22:19:28 UTC

Parallelism

88/100

Blocked

10%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,624,322  ·  17 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

0xc90d0183…ffe7

0x065c9d…c394

4 touches
1 conflict

0x93b13049…b5ae

0x065c9d…c394

3 touches
1 conflict

0xf504ad3c…0e45

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xbbe3312c…7de0

0x065c9d…c394

2 touches
0 conflicts

0xbd4c1704…833d

0x065c9d…c394

2 touches
0 conflicts

0xd15d6c31…357d

0x065c9d…c394

2 touches
0 conflicts

0xffecfd22…afbc

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 0xc90d0183c7…0bffe7

← previous block·next block →recent activity