← previous blocknext block →recent activity

Analyzing

Block #74,333,636

13 transactions · 11 stateful · 2026-05-13 13:57:04 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,333,636  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x152ff04b…91b3

0x34b655…2a6f

2 touches
0 conflicts

0x2734e46d…e50d

0x34b655…2a6f

2 touches
0 conflicts

0x3c9a8d84…4934

0x34b655…2a6f

2 touches
0 conflicts

0x3ef048a8…2e02

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity