← previous blocknext block →recent activity

Analyzing

Block #74,232,136

18 transactions · 16 stateful · 2026-05-13 02:42:03 UTC

Parallelism

72/100

Blocked

38%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,232,136  ·  18 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0xb2bda108…6927

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x061fe564…4092

0xd32edf…ff58

3 touches
1 conflict

0x3b2ea7fc…bc35

0x065c9d…c394

3 touches
1 conflict

0xcf7e8637…74ea

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity