← previous blocknext block →recent activity

Analyzing

Block #74,338,353

13 transactions · 13 stateful · 2026-05-13 14:28:28 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,338,353  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0xbf25e763…684f

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x776059…1d8d

4 touches
1 conflict

0x00000000…0001

0x776059…1d8d

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x44ad89ba…cf83

0xde22b2…7777

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity