← previous blocknext block →recent activity

Analyzing

Block #74,767,642

19 transactions · 16 stateful · 2026-05-15 14:16:16 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,767,642  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xb9868b52…c77f

0x34b655…2a6f

8 touches
6 conflicts

0xb138d087…4689

0x34b655…2a6f

6 touches
3 conflicts

0x5ffc25fa…b119

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x6434c774…f635

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x84fb2a36…db89

0x34b655…2a6f

4 touches
2 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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity