← previous blocknext block →recent activity

Analyzing

Block #74,335,777

19 transactions · 14 stateful · 2026-05-13 14:11:17 UTC

Parallelism

74/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,335,777  ·  19 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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4f65429e…2884

0x6657d1…8ccc

4 touches
1 conflict

0x81955a0a…29ee

0x6657d1…8ccc

4 touches
1 conflict

0xeeb8b7fc…24d6

0x6657d1…8ccc

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