← previous blocknext block →recent activity

Analyzing

Block #74,620,290

16 transactions · 11 stateful · 2026-05-14 21:52:38 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,620,290  ·  16 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

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x694b052d…3904

0x34b655…2a6f

4 touches
1 conflict

0x7c14c3db…11a8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xfdc9ea…8789

4 touches
1 conflict

0x44ad89ba…cf83

0x23c26b…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 0xfd784183e1…ab67bb

← previous block·next block →recent activity