← previous blocknext block →recent activity

Analyzing

Block #74,338,329

28 transactions · 20 stateful · 2026-05-13 14:28:18 UTC

Parallelism

57/100

Blocked

75%

Avg conflicts / tx

2.61

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,338,329  ·  28 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xbf5ce486…7288

0xd32edf…ff58

23 touches
66 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x99990df4…7131

0x065c9d…c394

3 touches
1 conflict

0xe6e91a85…94b8

0x065c9d…c394

3 touches
1 conflict

0xaeee3257…09a8

0x065c9d…c394

3 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: 0xd32edf66…9fff58

66 conflicts on slot 0xbf5ce48668…b87288

← previous block·next block →recent activity