← previous blocknext block →recent activity

Analyzing

Block #74,654,417

16 transactions · 14 stateful · 2026-05-15 01:40:08 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

0.88

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,654,417  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x18f3bb01…b130

0x065c9d…c394

5 touches
3 conflicts

0x4bcddb60…659e

0x065c9d…c394

5 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

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

6 conflicts on slot 0xffe431af56…838faa

← previous block·next block →recent activity