← previous blocknext block →recent activity

Analyzing

Block #74,430,662

31 transactions · 29 stateful · 2026-05-14 00:42:45 UTC

Parallelism

74/100

Blocked

62%

Avg conflicts / tx

1.87

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,430,662  ·  31 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

0xe6455d1f…1029

0x754704…b603

16 touches
28 conflicts

0x0d0b2509…074d

0x3bd359…433a

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0xd3470959…879c

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

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: 0x754704bc…afb603

28 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity