← previous blocknext block →recent activity

Analyzing

Block #74,476,098

32 transactions · 26 stateful · 2026-05-14 05:45:08 UTC

Parallelism

78/100

Blocked

46%

Avg conflicts / tx

0.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,476,098  ·  32 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

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x36f4b4f0…0188

0x34b655…2a6f

4 touches
1 conflict

0x537e2e5b…c3ab

0x34b655…2a6f

4 touches
1 conflict

0x5675c293…17d9

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity