← previous blocknext block →recent activity

Analyzing

Block #74,298,282

15 transactions · 13 stateful · 2026-05-13 10:01:56 UTC

Parallelism

60/100

Blocked

54%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,298,282  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0xff5c097d…680c

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b97d40a…09ed

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity