← previous blocknext block →recent activity

Analyzing

Block #74,775,130

22 transactions · 12 stateful · 2026-05-15 15:06:24 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.59

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,775,130  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

8 touches
6 conflicts

0xfbbc35e2…f66b

0x34b655…2a6f

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0x5ffc25fa…b119

0x34b655…2a6f

6 touches
3 conflicts

0x849f3e33…c095

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x7170c140…36bc

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity