← previous blocknext block →recent activity

Analyzing

Block #74,403,519

21 transactions · 19 stateful · 2026-05-13 21:42:06 UTC

Parallelism

24/100

Blocked

79%

Avg conflicts / tx

5.71

Longest chain

16 deep

Execution timeline

did this block parallelize well?

view

block #74,403,519  ·  21 txs across 16 waves  ·  depth 16
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

wave w15

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

0xaf7c2ffc…5a6f

0x3bd359…433a

32 touches
120 conflicts

0xdbde8233…3e76

0xdb8585…7777

32 touches
120 conflicts

0x00000000…0000

0xd004cf…da29

32 touches
120 conflicts

0x00000000…0001

0xd004cf…da29

32 touches
120 conflicts

0x00000000…0003

0xd004cf…da29

32 touches
120 conflicts

0x94ac3947…9d9f

0xdb8585…7777

2 touches
0 conflicts

0x966800b9…63dd

0xdb8585…7777

2 touches
0 conflicts

0x9cf298d1…1d7a

0xdb8585…7777

2 touches
0 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: 0x3bd359c1…15433a

120 conflicts on slot 0xaf7c2ffc57…fb5a6f

← previous block·next block →recent activity