← previous blocknext block →recent activity

Analyzing

Block #74,308,614

13 transactions · 12 stateful · 2026-05-13 11:10:42 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,308,614  ·  13 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

0x00bac013…a28c

0xfd44b3…00d1

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x1f3873a4…c80c

0x34b655…2a6f

6 touches
3 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa8abcc19…3d83

0xea1b8e…c5ec

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd8eb2d31…2ac0

0xea1b8e…c5ec

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: 0xfd44b351…7f00d1

3 conflicts on slot 0x00bac0131a…bba28c

← previous block·next block →recent activity