← previous blocknext block →recent activity

Analyzing

Block #74,423,789

18 transactions · 16 stateful · 2026-05-13 23:56:59 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,423,789  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7a499df7…2c47

0xd32edf…ff58

5 touches
3 conflicts

0xfc2f0550…d602

0x34b655…2a6f

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

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

3 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity