← previous blocknext block →recent activity

Analyzing

Block #74,449,998

17 transactions · 17 stateful · 2026-05-14 02:51:30 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,449,998  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xbb12db23…857e

0x34b655…2a6f

8 touches
6 conflicts

0xd40bddc1…773c

0x34b655…2a6f

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0x63d7ebf0…3dd9

0x34b655…2a6f

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 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

15 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity