← previous blocknext block →recent activity

Analyzing

Block #74,440,486

12 transactions · 11 stateful · 2026-05-14 01:48:11 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,440,486  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1c52541f…8670

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x26ee4e68…c417

0x34b655…2a6f

2 touches
0 conflicts

0x46356904…5ead

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity