← previous blocknext block →recent activity

Analyzing

Block #74,340,837

15 transactions · 14 stateful · 2026-05-13 14:44:59 UTC

Parallelism

80/100

Blocked

29%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,340,837  ·  15 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa8abf87d…faf3

0xd32edf…ff58

3 touches
1 conflict

0x16252d6c…3b7f

0x5e1b1a…7777

2 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x5593214e…dfc1

0x3bd359…433a

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

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

3 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity