← previous blocknext block →recent activity

Analyzing

Block #74,215,532

10 transactions · 9 stateful · 2026-05-13 00:51:39 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,215,532  ·  10 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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0xeea3f128…72db

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0xb6aedce9…a483

0x34b655…2a6f

4 touches
1 conflict

0x8b8e4020…11b0

0x34b655…2a6f

2 touches
0 conflicts

0xa3ff1ab2…8ae3

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

3 conflicts on slot 0xba3f84a54f…e54c26

← previous block·next block →recent activity