← previous blocknext block →recent activity

Analyzing

Block #74,363,443

8 transactions · 6 stateful · 2026-05-13 17:15:15 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,363,443  ·  8 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x3a48f05b…c360

0x1efe02…37d6

2 touches
0 conflicts

0x5190a894…c311

0x1efe02…37d6

2 touches
0 conflicts

0x6a897d91…b1f4

0x1efe02…37d6

2 touches
0 conflicts

0x00000000…0099

0xaa3145…feec

2 touches
0 conflicts

0x2f14f5c7…af89

0xaa3145…feec

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity