← previous blocknext block →recent activity

Analyzing

Block #74,765,233

41 transactions · 25 stateful · 2026-05-15 14:00:04 UTC

Parallelism

83/100

Blocked

48%

Avg conflicts / tx

0.66

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,765,233  ·  41 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0xcde4b977…60da

0xd32edf…ff58

7 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x4a8069e8…67cc

0x34b655…2a6f

4 touches
1 conflict

0x60af1366…1dfa

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity