← previous blocknext block →recent activity

Analyzing

Block #74,224,606

19 transactions · 17 stateful · 2026-05-13 01:52:02 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.74

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,224,606  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xba3f84a5…4c26

0x34b655…2a6f

8 touches
6 conflicts

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

4 touches
1 conflict

0x47b2d2eb…8aa5

0x34b655…2a6f

4 touches
1 conflict

0x6c11f784…15f2

0x34b655…2a6f

4 touches
1 conflict

0x73f4551d…4188

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

6 conflicts on slot 0xba3f84a54f…e54c26

← previous block·next block →recent activity