← previous blocknext block →recent activity

Analyzing

Block #74,182,650

14 transactions · 12 stateful · 2026-05-12 21:13:01 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,182,650  ·  14 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

0x768cffcd…2648

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0xc12b04b0…884b

0x34b655…2a6f

6 touches
3 conflicts

0xfcbe8228…8938

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x01744741…e4a3

0xd32edf…ff58

5 touches
3 conflicts

0xa16d205a…de20

0x34b655…2a6f

4 touches
1 conflict

0xb1406cb1…95b1

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 0x768cffcdb0…d12648

← previous block·next block →recent activity