← previous blocknext block →recent activity

Analyzing

Block #74,920,043

40 transactions · 25 stateful · 2026-05-16 07:13:03 UTC

Parallelism

80/100

Blocked

48%

Avg conflicts / tx

0.7

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,920,043  ·  40 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xd3d8b6bc…9063

0x34b655…2a6f

8 touches
6 conflicts

0x7af0ec11…0d61

0xd32edf…ff58

7 touches
6 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xeeb38aa7…8f00

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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

← previous block·next block →recent activity