← previous blocknext block →recent activity

Analyzing

Block #74,406,779

16 transactions · 16 stateful · 2026-05-13 22:03:50 UTC

Parallelism

50/100

Blocked

44%

Avg conflicts / tx

1.44

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,406,779  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xfac43f12…b842

0x34b655…2a6f

6 touches
3 conflicts

0xf10e4ac5…2f88

0x34b655…2a6f

6 touches
3 conflicts

0x050a4348…907a

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity