← previous blocknext block →recent activity

Analyzing

Block #74,255,141

10 transactions · 9 stateful · 2026-05-13 05:15:00 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,255,141  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf5c1c8ac…9874

0x065c9d…c394

2 touches
0 conflicts

0x44ad89ba…cf83

0x23c26b…7777

2 touches
0 conflicts

0x81a7ba4d…8c4b

0x23c26b…7777

2 touches
0 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity