← previous blocknext block →recent activity

Analyzing

Block #74,803,989

28 transactions · 22 stateful · 2026-05-15 18:19:05 UTC

Parallelism

61/100

Blocked

64%

Avg conflicts / tx

1.39

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,803,989  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x9c168b41…7486

0x34b655…2a6f

6 touches
3 conflicts

0xd11dc26e…59ab

0x34b655…2a6f

6 touches
3 conflicts

0xc7111d3a…296b

0x34b655…2a6f

6 touches
3 conflicts

0xb77c59ad…4c74

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity