← previous blocknext block →recent activity

Analyzing

Block #74,638,043

10 transactions · 8 stateful · 2026-05-14 23:50:58 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,638,043  ·  10 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

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xccc0ee2b…9f43

0x065c9d…c394

3 touches
1 conflict

0x00000000…0003

0x094452…0a09

2 touches
0 conflicts

0x00000000…0004

0x094452…0a09

2 touches
0 conflicts

0x76f2524a…306c

0x3bd359…433a

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 0x30276c1c08…7247b4

← previous block·next block →recent activity