← previous blocknext block →recent activity

Analyzing

Block #74,637,899

8 transactions · 7 stateful · 2026-05-14 23:50:01 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,637,899  ·  8 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x5f0bed97…e6d2

0x065c9d…c394

4 touches
1 conflict

0xd9f8637f…a16a

0x065c9d…c394

3 touches
1 conflict

0x34c276a2…06b2

0x065c9d…c394

3 touches
1 conflict

0xcb45efea…0b58

0x065c9d…c394

3 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

2 touches
0 conflicts

0x00000000…0002

0x63e48b…53f2

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

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity